Skip to main content

AMI AptioV CVE-2025-58774

| EUVDEUVD-2025-211078 HIGH
Buffer Access with Incorrect Length Value (CWE-805)
2026-10-13 AMI GHSA-28hr-x2jf-jpxf
8.3
CVSS 4.0 · Vendor: AMI
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Gain local low-privileged access
  2. Delivery
    Craft input with incorrect length value
  3. Exploit
    Trigger buffer overread/overflow in BIOS
  4. Execution
    Execute code in firmware context
  5. Impact
    Corrupt memory / persist below OS

Vulnerability Assessment

Weakness
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Buffer access bounds checking
Exploitation Conditions

Requires local access to a system running AMI Aptio V (APTIOV) UEFI BIOS plus low-level privileges (PR:L) sufficient to reach the vulnerable firmware interface that mishandles a buffer length value (CWE-805); there is no network vector (AV:L) and no user interaction is needed (UI:N). Limiting factors for defenders: the attacker must already have local code execution or privileged OS-level access on the target, the flaw is not remotely exploitable, no public exploit exists, and remediation depends on the OEM/board vendor shipping the AMI firmware fix - meaning real-world exposure is highest on physically accessible, multi-tenant, or already-compromised hosts rather than internet-facing attack surface.

Impact

This is a credible but second-tier priority. The CVSS 4.0 vector (AV:L/AC:L/AT:N/PR:L/UI:N) scores 8.3 (High), but the key downgrading signal is the LOCAL attack vector combined with required privileges (PR:L) - this is not remotely reachable. The input provides no EPSS score, the CVE is NOT in CISA KEV, and no POC is referenced, so there is no public exploit identified at time of analysis and no evidence of active exploitation. The impact profile is skewed: the vendor vector rates confidentiality and integrity as Low (VC:L/VI:L) but availability as High (VA:H), with subsequent-system availability also High (SA:H), indicating the primary realistic outcome is firmware/system availability loss and corruption rather than clean data theft - this slightly tempers the 'arbitrary code execution' language in the description. Firmware-level code execution is inherently high-value (pre-OS, persistence, defense evasion potential), which raises the ceiling, but the local-access precondition and absence of exploitation signals mean this is a patch-on-normal-cadence issue for most fleets rather than an emergency, with priority elevated only for high-assurance or physically exposed systems. Note a tension to verify: the description's 'arbitrary code execution' at BIOS level would typically justify higher C/I impact than the vendor's VC:L/VI:L - the limited detail in the advisory means exact exploit primitive should be confirmed with AMI.

Exploit ScenarioDerived

A local, low-privileged attacker (or malware already running on the host) supplies a crafted input to a vulnerable AMI Aptio V BIOS interface whose length field is mishandled (CWE-805), triggering a buffer overflow and memory corruption in firmware context that can escalate to code execution below the OS. No public exploit code is referenced, and exploitation requires existing local access rather than a network entry point.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
No patch listed yet 0.1% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 13, 2026

Local attackers with low-level privileges can cause buffer overflows and memory corruption in AMI AptioV UEFI firmware by supplying malformed length values to a firmware interface, potentially leading to arbitrary code execution within the BIOS/SMM environment. The vulnerability (CWE-805) affects AptioV-based firmware across OEM platforms and requires local access plus existing OS-level privileges; no public exploit identified at time of analysis. Due to the local attack vector and dependency on OEM firmware updates, this is assessed as a credible but second-tier priority.

RemediationAI

No specific patched version is provided in the available data; consult AMI advisory AMI-SA-2026002 for OEM-specific firmware updates, as remediation depends on the OEM/board vendor shipping the updated AptioV firmware. Until a patch is applied, restrict local administrator privileges (required for exploitation) to trusted users, enable BIOS write protection and SMM lockdown features to prevent unauthorized firmware modifications (note that this may block legitimate updates until disabled), and implement measured boot with TPM attestation to detect tampering. These controls reduce the attack surface but require administrative overhead and may impact system manageability.

Affected VersionsENISA

AptioV AptioV_5.0 <AptioV_5.043

Affects your stack

Find out whether the stacks and servers you run are on an affected version.

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The vulnerability resides in AMI AptioV, a UEFI firmware reference implementation used by many motherboard and system OEMs. CWE-805 (Buffer Access with Incorrect Length Value) occurs when firmware code trusts a length field without validating it against the actual buffer size, allowing out-of-bounds reads or writes. In this case, a local attacker with low-level privileges (PR:L) can invoke the vulnerable interface, corrupt memory in the firmware environment, and potentially achieve arbitrary code execution in System Management Mode (SMM) or at runtime. The CPE cpe:2.3:a:ami:aptiov:*:*:*:*:*:*:*:* indicates all versions are potentially affected, and exploitation requires local access (AV:L) without user interaction (UI:N). The CVSS v3.1 assessment (AV:L/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:H) confirms scope change and high availability impact.

Know when Aptiov gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (AMI) PRIMARY 8.3 HIGH
CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:H/SC:L/SI:L/SA:H
vuln.today AI 7.9 HIGH

Local privileged trigger (AV:L/PR:L), firmware execution crosses into the broader system so S:C; availability dominant (A:H) with limited confidentiality/integrity per vendor impact mapping.

3.1 AV:L/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:H
4.0 AV:L/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:H/SC:L/SI:L/SA:H

Primary rating from Vendor (AMI).

CVSS VectorVendor: AMI

Attack Vector
Local
Attack Complexity
Low
Attack Requirements
None
Privileges Required
Low
User Interaction
None
Vulnerable system: Confidentiality
Low
Vulnerable system: Integrity
Low
Vulnerable system: Availability
High
Subsequent system: Confidentiality
Low
Subsequent system: Integrity
Low
Subsequent system: Availability
High

DescriptionCVE.org

AMI APTIOV contains vulnerabilities in BIOS where users may cause “Buffer Access with Incorrect Length Value” 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.

Executive ViewAI

Why It Matters

AMI AptioV UEFI firmware used across OEM platforms contains a high-severity flaw that could allow a local attacker with low-level privileges to corrupt memory and potentially execute code within BIOS/SMM. This creates organizational risk because firmware-level compromise can persist below the operating system and may require OEM-specific remediation, affecting endpoint and server fleets that rely on affected firmware. No public exploit identified at time of analysis, and no vendor-released patch identified at time of analysis, making this a credible but second-tier priority pending OEM updates.

Business Impact: High
Compensating Controls

No vendor-released patch identified at time of analysis; interim mitigations include restricting local OS privileges, enforcing least privilege, enabling Secure Boot and firmware TPM measurements, monitoring AMI/OEM advisories for AptioV firmware updates, and applying OEM firmware updates as soon as they become available.

Threat Intelligence Overview

EPSS Score
0.1%
Top 98% exploitable
Prevalence
High
AMI Aptio V UEFI firmware ships on a very large share of x86 OEM systems
Data Quality
5 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.1%
Patch available No
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation· derived
None
System Exposure· derived
Small
Automatable· derived
No
Human Impact
High

Priority Score

42
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +42
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

A buffer overflow occurs when a program writes more data to a memory buffer than it was allocated to hold, causing the excess data to spill into adjacent memory regions.

Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy