Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessGain privileged local code execution
-
DeliveryInvoke vulnerable BIOS interface/handler
-
ExploitTrigger out-of-bounds write (CWE-787)
-
ExecutionCorrupt firmware memory and execute code
-
ImpactEstablish firmware/SMM-level persistence
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Bounds checking, write limits
MITRE ATT&CK
2 techniques across 2 tactics: Execution, Privilege Escalation The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires LOCAL access to a system running AMI Aptio V (APTIOV) BIOS AND pre-existing HIGH privileges (PR:H - e.g. administrator/kernel-level code execution), with no user interaction (UI:N). The out-of-bounds write is in BIOS code and affects the default firmware (no special feature toggle is cited in the advisory text). Key LIMITING factors: the HIGH attack complexity (AC:H) implies the attacker must meet specific state/timing or configuration preconditions to control the write, and the requirement for prior privileged local access means this cannot be reached by a remote or unauthenticated attacker - it is a privilege-escalation/firmware-persistence primitive rather than an initial-access vulnerability. |
| Impact | This is a genuine but constrained firmware-level risk rather than a mass-exploitation emergency. The CVSS 4.0 vector (AV:L/AC:H/PR:H/UI:N, base 7.1 High) is the dominant signal and it points away from easy exploitation: an attacker needs LOCAL access (AV:L), already-HIGH privileges (PR:H), and must overcome HIGH attack complexity (AC:H). Against that, the vulnerable-system impact is severe across all three pillars (VC:H/VI:H/VA:H) with limited subsequent-system impact (SC:L/SI:L/SA:L), which is consistent with an out-of-bounds write (CWE-787) in BIOS/UEFI that can yield memory corruption and arbitrary code execution at the firmware/SMM level. No EPSS score, no CISA KEV listing, and no public POC were provided in the input, so there is no public exploit identified at time of analysis. The combination of high required privileges, local-only vector, and high complexity means this is a targeted/post-compromise privilege-and-persistence concern (firmware foothold) rather than a widely automatable attack - real priority for high-security and OEM supply-chain contexts, lower immediate urgency for general fleets. Note the input CVSS is 4.0 only; no CVSS 3.1 vector or EPSS was supplied, so exploitation-probability signals are missing and cannot corroborate or contradict the vector. |
| Exploit ScenarioDerived | A local attacker who has already gained privileged (administrator/kernel-level) code execution on a system running AMI Aptio V firmware triggers a crafted condition that causes an out-of-bounds write in BIOS code, corrupting memory to execute arbitrary code at the firmware/SMM level. Because attack complexity is high, the attacker must satisfy specific timing or state preconditions to reliably control the write. No public exploit code was identified in the provided intelligence. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 13, 2026
An out-of-bounds write (CWE-787) in AMI Aptio V (APTIOV) BIOS firmware can be triggered by a local attacker who already holds high privileges, potentially corrupting memory inside firmware code paths and enabling buffer overflows, arbitrary code execution, and loss of confidentiality, integrity, and availability. Successful abuse requires local access plus pre-existing administrative or kernel-level privileges, and the high attack complexity means specific state, timing, or configuration preconditions must be met before the write can be controlled, so this is best characterized as a firmware persistence/privilege-escalation primitive rather than an initial-access or remote attack vector. At time of analysis there is no public exploit identified, no CISA KEV listing, and no confirmed exact fix version in the available data, though AMI has issued security advisory AMI-SA-2026002 covering the issue.
RemediationAI
Apply the BIOS/firmware update that carries the AMI fix, as described in AMI security advisory AMI-SA-2026002 (https://go.ami.com/hubfs/Security%20Advisories/2026/AMI-SA-2026002.pdf); an exact fixed version is not confirmed in the available data, so obtain the corresponding BIOS release directly from your system OEM, which is the only party that can deliver a signed, flashable image for your specific hardware. Because exploitation requires local access with pre-existing high privileges (PR:H) and high attack complexity, the most effective compensating controls are limiting who can obtain administrative or kernel-level local access, enforcing Secure Boot and firmware write protections, and maintaining TPM-based measured boot so that any tampering with firmware is detectable - the trade-off is that measured boot and firmware attestation add management overhead and can cause boot friction if the attestation policy is misconfigured. Platform-specific hardening such as enabling BIOS write protection, requiring a firmware/administrator password for flash operations, and disabling unnecessary UEFI network or pre-boot shell boot options reduces the reachable attack surface, at the cost of complicating legitimate firmware servicing. Organizations should also monitor for abnormal firmware modification attempts and treat a compromised device as requiring full re-flash rather than a software-only cleanup, since memory corruption in BIOS code can persist below the operating system.
Affected VersionsENISA
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
AMI Aptio V is a widely licensed UEFI/BIOS firmware platform used by numerous OEM system builders, and the affected CPE cpe:2.3:a:ami:aptiov:*:*:*:*:*:*:*:* indicates the vendor has not published a version-bounded range, so all builds of the Aptio V line should be treated as potentially affected until OEM-specific firmware revisions are mapped. The root cause class is CWE-787 Out-of-bounds Write: the firmware fails to correctly validate the size or bounds of a buffer before writing to it, which in the UEFI context typically surfaces inside a driver, SMI handler, or setup variable parsing path. Because the vulnerable code runs in a highly privileged firmware context, a successful write primitive can corrupt adjacent memory structures, leading to buffer overflows and memory corruption that may ultimately yield arbitrary code execution with firmware-level trust - the strongest position from which to subvert Secure Boot, persist across OS reinstalls, or undermine later security controls. The CVSS:4.0 vector supplied by the vendor (AV:L/AC:H/AT:N/PR:H/UI:N, high VC/VI/VA with low subsequent-system impact) aligns with the independent assessment (CVSS:3.1 AV:L/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H): the attack is local, needs prior high privilege, requires no user interaction, and demands elevated complexity rather than a straightforward memory-corruption trigger.
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
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
Local-only BIOS flaw reachable only with prior high privileges (AV:L/PR:H) and nontrivial preconditions (AC:H); full code execution gives C:H/I:H/A:H.
Primary rating from Vendor (AMI).
CVSS VectorVendor: AMI
DescriptionCVE.org
AMI APTIOV contains vulnerabilities in BIOS where users may cause "Out-of-bounds Write” 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
AMI Aptio V BIOS firmware, widely used in enterprise endpoints, contains a high-severity out-of-bounds write flaw that could let an attacker with existing administrative or kernel-level access achieve persistent firmware compromise, undermining OS security and complicating remediation. Organizations relying on this firmware face increased risk of stealthy, long-term persistence and potential loss of data integrity, though exploitation requires local access and elevated privileges. Leadership should prioritize understanding exposure and preparing for potential firmware-level incident response until a vendor patch is available.
Interim mitigations include restricting local administrative and kernel-level access, enabling Secure Boot and TPM-based firmware attestation, monitoring for anomalous firmware modifications, and applying vendor patch when released per AMI-SA-2026002.
Threat Intelligence Overview
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.
What every action level means
SSVC AssessmentENISA
Priority Score
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.
Memory corruption occurs when a program writes data beyond the boundaries of allocated memory regions or accesses memory in unintended ways, violating the integrity of the process's address space.
Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.
Arbitrary code execution in AMI APTIOV BIOS firmware is achievable by a locally-present privileged user exploiting an in
Local attackers with low-level privileges can cause buffer overflows and memory corruption in AMI AptioV UEFI firmware b
A classic buffer overflow (CWE-120) in AMI Aptio V UEFI/BIOS firmware allows a local user holding low-level privileges t
Integer overflow in AMI AptioV BIOS firmware, classified as CWE-190, can be triggered by a local high-privileged caller
Local information disclosure in AMI Aptio V BIOS/UEFI firmware allows low-privileged local attackers to access sensitive
EUVD-2025-211077
GHSA-vpw8-537w-hff5
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB