CyberSecBulletin
CVE-2026-93495NVD status: Awaiting Analysis

Motherboard(PRIME Z390-A ): Improper Initialization

Published Updated By the CyberSecBulletin desk

CVE-2026-93495 is a high-severity improper initialization vulnerability in Motherboard(PRIME Z390-A ) from ASUS, with a CVSS 4.0 base score of 7.0 out of 10. It can be exploited with physical access to the device by an unauthenticated attacker, without any action from a user. Affected Motherboard(PRIME Z390-A ) versions: through 2101. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 0.16% chance of exploitation within 30 days, which is low compared with other CVEs.

Next patch cycle

High severity with no evidence of exploitation so far.

What to do

  1. Check which version of Motherboard(PRIME Z390-A ) you run against the affected versions below, and install the vendor's latest release.
  2. Read the advisory on asus.com for workarounds and exact fixed builds.

Affected products and versions

VendorProductAffected versionsFixed in
ASUSMotherboard(PRIME Z390-A )through 2101Not stated
ASUSMotherboard(PRIME Z390-A/H10 )through 2101Not stated
ASUSMotherboard(ROG MAXIMUS XI HERO )through 2101Not stated
ASUSMotherboard(ROG MAXIMUS XI HERO (WI-FI) )through 2101Not stated
ASUSMotherboard(ROG MAXIMUS XI FORMULA )through 2101Not stated
ASUSMotherboard(ROG MAXIMUS XI CODE )through 2101Not stated
ASUSMotherboard(ROG MAXIMUS XI EXTREME )through 2101Not stated
ASUSMotherboard(ROG MAXIMUS XI APEX )through 2101Not stated
ASUSMotherboard(ROG MAXIMUS XI GENE )through 2101Not stated
ASUSMotherboard(ROG STRIX Z390-E GAMING )through 2101Not stated
ASUSMotherboard(ROG STRIX Z390-F GAMING )through 2101Not stated
ASUSMotherboard(Pro WS C246-ACE )through 2101Not stated
ASUSMotherboard(WS Z390 PRO )through 1401Not stated

Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
PhysicalThe attacker must physically touch the device.
Attack complexity
LowNo special conditions are needed; the attack works reliably.
Attack requirements
NoneThe attack does not depend on a particular deployment or configuration.
Privileges required
NoneNo account or login is needed.
User interaction
NoneNo action by a victim is required.
Confidentiality (vulnerable system)
HighSerious loss of confidentiality on the vulnerable system.
Integrity (vulnerable system)
HighSerious loss of integrity on the vulnerable system.
Availability (vulnerable system)
HighSerious loss of availability on the vulnerable system.
Confidentiality (other systems)
NoneNo loss of confidentiality on systems beyond the vulnerable one.
Integrity (other systems)
NoneNo loss of integrity on systems beyond the vulnerable one.
Availability (other systems)
NoneNo loss of availability on systems beyond the vulnerable one.

Vector: CVSS:4.0/AV:P/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X. Scored by CNA.

Official description

Improper initialization in an ASUS certain motherboard allows an physically proximate user to read or write arbitrary memory by inserting a specially crafted device. Refer to the ' Security Update for Multiple ASUS Motherboards ' section on the ASUS Security Advisory for more information.

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Improper Initialization

The product does not initialize or incorrectly initializes a resource.

How developers prevent this class of flaw

  • Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. For example, in Java, if the programmer does not explicitly initialize a variable, then the code could produce a compile-time error (if the variable is local) or automatically initialize the variable to the default value for the variable's type. In Perl, if explicit initialization is not performed, then a default value of undef is assigned, which is interpreted as 0, false, or an equivalent value depending on the context in which the variable is accessed.
  • Identify all variables and data stores that receive information from external sources, and apply input validation to make sure that they are only initialized to expected values.
  • Explicitly initialize all your variables and other data stores, either during declaration or just before the first usage.

More Improper Initialization vulnerabilities (CWE-665)

Timeline

  1. CVE record published.
  2. CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
  3. Record last changed materially (score, affected products, status or references).

References

Recent Improper Initialization vulnerabilities

Spotted an error? Tell us.