# CVE-2025-58771: UEFI OOB Write and Buffer Overflow Vulnerabilities

> Local attackers can exploit integer overflows in AMI AptioV BIOS to trigger buffer overflows, leading to arbitrary code execution and privilege escalation.

- **Severity:** High 7.1 (`CVSS:4.0/AV:L/AC:H/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:L/SI:L/SA:L`)
- **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:** 13 Oct 2026
- **Updated:** 13 Oct 2026
- **Also known as:** GHSA-fw3j-xvmr-h427

## What is CVE-2025-58771?

CVE-2025-58771 is a high-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 vulnerabilities in BIOS
where users may cause “Integer Overflow or Wraparound” by local access. Successful exploitation of this vulnerability could
lead to buffer overflows, memory corruption, and arbitrary code execution, and
also impact Confidentiality, Integrity, and Availability.

Weakness: CWE-190 (Integer Overflow or Wraparound)

## Which versions are affected by CVE-2025-58771?


## How do I fix CVE-2025-58771?

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

## Is CVE-2025-58771 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-58771 and fix it if it is affected.

What it is: CVE-2025-58771 is a high-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-2025-58771 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-2025-58771/ (Markdown: https://insights.sbomify.com/CVE-2025-58771/index.md)
```

## Sources

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

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