# CVE-2026-19398: Memory corruption in FA507NU

> A local administrator can trigger a system crash or BIOS corruption via an out-of-bounds write in the ASUS BIOS SMM module.

- **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
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Aug 2026
- **Updated:** 9 Sep 2026
- **Also known as:** GHSA-mqcp-4543-826g

## What is CVE-2026-19398?

CVE-2026-19398 is a medium-severity memory corruption vulnerability in ASUS FA507NU, published on 27 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An out-of-bounds write in the SmiFlash SMM module of ASUS FA507NU and FA507NV BIOS allows a local  administrator to cause a system crash (BSOD) or BIOS corruption via a crafted software SMI (SW SMI) request with an oversized length value.Refer to the ' 
Security Update for ASUS FA507NV / FA507NU BIOS   ' section on the ASUS Security Advisory for more information.

Weakness: CWE-787 (Out-of-bounds Write)

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


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

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

## Is CVE-2026-19398 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-19398 is a medium-severity memory corruption vulnerability in ASUS FA507NU, published on 27 Aug 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-19398 in the wild and no public exploit code.

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

## Sources

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

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