Skip to content
major vulnerability· requires attention

AMI AptioV BIOS is widely deployed across OEM desktops/servers; a BIOS-level arbitrary code execution can enable persistent, organization-wide compromise.

Systems

CVE-2026-33197

8.7
High
EPSS 0.12%Patch availableSep 11, 2026

AMI AptioV BIOS flaw allows local privileged user to execute arbitrary code.

common questions

Is CVE-2026-33197 being exploited?

Not confirmed. CVE-2026-33197 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. EPSS currently estimates a 0.12% probability of exploitation in the next 30 days.

How severe is CVE-2026-33197?

CVE-2026-33197 is rated High with a CVSS score of 8.7. 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-2026-33197?

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

What does CVE-2026-33197 affect?

CVE-2026-33197 affects AMI AptioV BIOS, OEM systems using AMI AptioV (desktops/laptops/servers). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-33197?

Apply AMI vendor BIOS updates immediately and verify firmware versions.

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

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

Local privileged user can achieve arbitrary code execution in BIOS, enabling firmware compromise, persistence, and full system control (C/I/A loss).

action required

Immediate action required

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

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