# CVE-2026-93495: Other in Motherboard(PRIME Z390-A )

> A physically proximate attacker can read or write arbitrary memory on ASUS motherboards by inserting a specially crafted device due to improper initialization.

- **Severity:** High 7.0 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Oct 2026
- **Updated:** 5 Oct 2026
- **Also known as:** GHSA-4pjr-762p-4q8c

## What is CVE-2026-93495?

CVE-2026-93495 is a high-severity vulnerability in ASUS Motherboard(PRIME Z390-A ), published on 1 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### 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.

Weakness: CWE-665 (Improper Initialization)

## Which versions are affected by CVE-2026-93495?


## How do I fix CVE-2026-93495?

No fix has been published for CVE-2026-93495 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-93495 being exploited?

There is no known exploitation of CVE-2026-93495 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-93495 and fix it if it is affected.

What it is: CVE-2026-93495 is a high-severity vulnerability in ASUS Motherboard(PRIME Z390-A ), published on 1 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-93495 in the wild and no public exploit code.

Affected product: ASUS Motherboard(PRIME Z390-A ). No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-93495/ (Markdown: https://insights.sbomify.com/CVE-2026-93495/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-93495
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-93495
- OSV: https://osv.dev/vulnerability/CVE-2026-93495

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-93495/
Summaries are generated and may contain mistakes; the official description above is the record.