Which versions are affected?

Affected product and version evidence is listed in the product table above. Current public advisories should be checked for exact version scope before patch targeting is finalized.

Is there active exploitation?

Active exploitation is not confirmed from current sources for CVE-2026-93495. If exploitation is not confirmed from current sources, teams should document that status and continue monitoring KEV, vendor, and telemetry updates.

No. CVE-2026-93495 is not listed in CISA KEV in the supplied enrichment data. KEV status should be monitored because it can change after initial disclosure or after exploitation becomes publicly confirmed.

Is there a public exploit?

1 public PoC repositories reported; 0 marked weaponized in current dataset. Public exploit or PoC availability should raise triage priority, especially for exposed or business-critical systems.

How can defenders detect it?

Start with Not reported where available. Look for vulnerability-class behavior, product errors, suspicious authentication events, exploit probes, and abnormal process activity based only on evidence that applies to the affected product.

How should teams prioritize it?

Prioritize CVE-2026-93495 using CVSS 7, EPSS 0%, KEV status, public PoC status, and asset exposure. Internet-facing, privileged, or business-critical deployments should be handled first.

Are workarounds available?

The supplied mitigation guidance says to apply vendor patches and restrict external exposure until fixed. Fixed-version evidence is listed in the mitigation section above.

Which threat actors are linked publicly?

No public threat actor linkage is confirmed from current sources. Do not attribute exploitation to a threat actor unless the source evidence explicitly supports that linkage.

What should be done in the next 24 hours?

Identify exposed assets running affected vendor/product/version combinations. Prioritize based on EPSS, PoC availability, and external exposure. Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class. Open remediation tickets with affected assets, owners, evidence status, and detection coverage so decisions are traceable.

highpublic exploit

CVE-2026-93495

CVE-2026-93495 — Improper initialization in an ASUS certain motherboard allows an physically proximate user to read or write arbitrary memory by inserting a…

Improper initialization in an ASUS certain motherboard allows an physically proximate user to read or write arbitrary memory by inserting a specially crafted device.

Published Oct 1, 2026Updated Oct 1, 2026Sources: NVD, ASUS (CNA), GitHub, GitHub Security Advisory, SOCRadar CTI

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.

Exploitation

Exploit code

public exploit, none observed

EPSS

ahead of 0% of scored CVEs

Affects

ASUS

13 products listed

CVSS base

high

Remediation

The vendor's own words where we have them.

Upgrade Motherboard(PRIME Z390-A ) to a fixed release. Apply vendor patches per advisory and restrict external exposure of the affected component until patched.

First 24 hours

Ordered from the record's own fields — exposure first, because you cannot patch what you have not found.

Identify exposed assets running affected vendor/product/version combinations.
Prioritize based on EPSS, PoC availability, and external exposure.
Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class.

Affected scope

Vendor, product and version as the advisories word them.

Vendor	Product	Versions	Status
ASUS	Motherboard(PRIME Z390-A )	through 2101	Vulnerable
ASUS	Motherboard(PRIME Z390-A/H10 )	through 2101	Vulnerable
ASUS	Motherboard(ROG MAXIMUS XI HERO )	through 2101	Vulnerable
ASUS	Motherboard(ROG MAXIMUS XI HERO (WI-FI) )	through 2101	Vulnerable
ASUS	Motherboard(ROG MAXIMUS XI FORMULA )	through 2101	Vulnerable
ASUS	Motherboard(ROG MAXIMUS XI CODE )	through 2101	Vulnerable
ASUS	Motherboard(ROG MAXIMUS XI EXTREME )	through 2101	Vulnerable
ASUS	Motherboard(ROG MAXIMUS XI APEX )	through 2101	Vulnerable
ASUS	Motherboard(ROG MAXIMUS XI GENE )	through 2101	Vulnerable
ASUS	Motherboard(ROG STRIX Z390-E GAMING )	through 2101	Vulnerable
ASUS	Motherboard(ROG STRIX Z390-F GAMING )	through 2101	Vulnerable
ASUS	Motherboard(Pro WS C246-ACE )	through 2101	Vulnerable

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Scope

Attack Complexity

Low

Attack Vector

Physical

Privileges Req

None

User Interaction

None

Every base score collected

Sources score independently and disagree; each row says who scored it and under which version.

Score	Version	Severity	Expl.	Impact	Source
7	CVSS 4.0	high	—	—	ASUS (CNA)

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

What this weakness leads to

MITRE's own consequences and mitigations for the weakness class — the authority's wording, not guidance derived from the CVSS vector.

MITRE

CWE-665 · Improper Initialization

Read Memory
Read Application Data
Bypass Protection Mechanism
DoS: Crash, Exit, or Restart

Mitigation: 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.

Weakness & attack patterns

CWE-665

Attack patterns reported against this CVE. The ATT&CK techniques below are inferred from its weakness class.

CAPEC-26 · Leveraging Race ConditionsCAPEC-29 · Leveraging Time-of-Check and Time-of-Use (TOCTOU) Race Conditions

Public exploit

Capability, not use: code existing is a different claim from anyone running it.

Repositories

Detection

Read off the CVSS vector and the weakness class. Starting points, not rules we have tested.

Monitor for scanner or exploit-pattern traffic after 1 public PoC repositories were reported.

Timeline

What happened to this CVE, newest first — with the readings a source repeats on a schedule counted underneath rather than listed.

2026
Added · CVSS 3.1 7.0 (AV:P)
Oct 1, 2026 · NVD
Initial · CVE published
Oct 1, 2026 · NVD
Added · GHSA-4pjr-762p-4q8c published (high)
Oct 1, 2026 · GitHub Security Advisory
CVE published by NIST.
Oct 1, 2026 · SOCRadar CTI

References

3 on the record

www.asus.com/security-advisory
Vendor Advisory, NIST
nvd.nist.gov/vuln/detail/CVE-2026-93495
NVD
github.com/advisories/GHSA-4pjr-762p-4q8c
Exploit, Third Party Advisory

Elsewhere on this site

ASUSevery CVE for this vendor
Unclassifiedsame class
CWE-665other pages naming this weakness

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record1

What should defenders know first?

CVE-2026-93495 is Improper initialization in an ASUS certain motherboard allows an physically proximate user to read or write arbitrary memory by inserting a…, a high vulnerability affecting Motherboard(PRIME Z390-A ), Motherboard(PRIME Z390-A/H10 ), Motherboard(ROG MAXIMUS XI HERO ), Motherboard(ROG MAXIMUS XI HERO (WI-FI) ), Motherboard(ROG MAXIMUS XI FORMULA ), Motherboard(ROG MAXIMUS XI CODE ), Motherboard(ROG MAXIMUS XI EXTREME ), Motherboard(ROG MAXIMUS XI APEX ), Motherboard(ROG MAXIMUS XI GENE ), Motherboard(ROG STRIX Z390-E GAMING ), Motherboard(ROG STRIX Z390-F GAMING ), Motherboard(Pro WS C246-ACE ), Motherboard(WS Z390 PRO ) from ASUS. The current evidence does not list it in CISA KEV, and the exploit status is: Active exploitation is not confirmed from current sources for CVE-2026-93495. Public exploit evidence is: 1 public PoC repositories reported; 0 marked weaponized in current dataset. The affected-version evidence is listed in the key facts and affected products tables. Defenders should first verify whether exposed or business-critical assets run those versions, then apply vendor patches or mitigations, restrict reachable attack surface, and preserve logs for detection review. CVSS 7 describes technical severity, while EPSS 0% helps estimate near-term exploit likelihood; neither replaces asset context. Unknown fields should remain explicit in tickets, and threat actor, IOC, victimology, or payload claims should not be added unless a cited source supports them. Monitor CISA KEV, vendor advisories, NVD changes, public PoC repositories, and internal telemetry for update triggers.