Skip to content
major vulnerability· requires attention

AMI AptioV is widely deployed OEM BIOS firmware; firmware-level RCE can persist across reboots and affect large fleets, causing broad operational impact.

Systems

CVE-2025-58774

8.3
High
EPSS n/aPatch availableOct 15, 2026

Local buffer overflow in AMI AptioV BIOS enabling arbitrary firmware code execution

common questions

Is CVE-2025-58774 being exploited?

Not confirmed. CVE-2025-58774 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked.

How severe is CVE-2025-58774?

CVE-2025-58774 is rated High with a CVSS score of 8.3. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2025-58774?

Yes. A fix has been recorded for CVE-2025-58774. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2025-58774 affect?

CVE-2025-58774 affects AMI AptioV BIOS, OEM desktops/laptops/servers using AptioV. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2025-58774?

Install AMI/OEM BIOS updates immediately; restrict local admin rights and verify firmware integrity.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
AMI AptioV BIOSOEM desktops/laptops/servers using AptioV
impact

Local attacker with OS access can trigger BIOS buffer overflow enabling arbitrary firmware code execution, persistence, and full system compromise.

action required

Immediate action required

affected versions
AMI AptioV
  • affected>= AptioV_5.0 and < AptioV_5.043

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free