# CVE-2026-88781: Untrusted Pointer Dereference in ASUS certain motherboards firmware allows a kernel-level privileges user can supply an arbitrary memory add


- **Severity:** Medium 6.8 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:H/UI:N/VC:N/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 27 Oct 2026
- **Updated:** 27 Oct 2026
- **Also known as:** GHSA-r2vp-5h4m-7j3c

## What is CVE-2026-88781?

CVE-2026-88781 is a medium-severity vulnerability in ASUS motherboards firmware, published on 27 Oct 2026. 

### Official description

Untrusted Pointer Dereference in ASUS certain motherboards firmware allows a kernel-level privileges user can supply an arbitrary memory address via an I/O command, leading to subsequent system information being tampered with or causing a system crash.
Refer to the 'Security Update for Multiple ASUS Motherboards' section on the ASUS Security Advisory for more information.

Weakness: CWE-822 (Untrusted Pointer Dereference)

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


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

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

## Is CVE-2026-88781 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-88781 is a medium-severity vulnerability in ASUS motherboards firmware, published on 27 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-88781 in the wild and no public exploit code.

Affected product: ASUS motherboards firmware. 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-88781/ (Markdown: https://insights.sbomify.com/CVE-2026-88781/index.md)
```

## Sources

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

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