# CVE-2026-0893: Uncleared Password Keystrokes Vulnerability

> Local attackers can access uncleared password keystrokes in AMI AptioV BIOS, leading to information disclosure and privilege escalation.

- **Severity:** Medium 5.8 (`CVSS:4.0/AV:L/AC:H/AT:N/PR:L/UI:N/VC:H/VI:L/VA:L/SC:L/SI:L/SA:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Oct 2026
- **Updated:** 13 Oct 2026
- **Also known as:** GHSA-gfm4-mgc8-f6ph

## What is CVE-2026-0893?

CVE-2026-0893 is a medium-severity vulnerability in AMI AptioV, published on 13 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

AMI APTIOV contains a vulnerability in BIOS
where an attacker may cause “Exposure of Sensitive
Information to an Unauthorized Actor” by local access. Successful
exploitation of this vulnerability can lead to information disclosure,
privilege escalation, and further impact on Confidentiality, Integrity, and
Availability.

Weakness: CWE-213 (Exposure of Sensitive Information Due to Incompatible Policies)

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


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

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

## Is CVE-2026-0893 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-0893 is a medium-severity vulnerability in AMI AptioV, published on 13 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-0893 in the wild and no public exploit code.

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

## Sources

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

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