Security readout for executives and security teams
Plain-English summary
This is a firmware boot-stage flaw in AMI Aptio 5.x. A highly privileged local attacker could run code very early in boot, before OS defenses, potentially bypassing mitigations and exposing VM or confidential computing secrets. The provided sources do not show active exploitation.
Executive priority
High priority for organizations running affected firmware on servers, virtualization infrastructure, or confidential-computing workloads. Start with firmware inventory and OEM guidance because the bundle does not provide a universal patch package or affected model list.
Technical view
CVE-2022-26873 is a CWE-121 stack buffer overflow in PlatformInitAdvancedPreMem during the PEI phase. Sources describe arbitrary code execution, influence over subsequent boot stages, possible SMRAM payload injection, and disclosure or isolation impacts. CVSS 3.1 is 8.2 with local access and high privileges required.
Likely exposure
Exposure is likely limited to systems whose firmware includes AMI Aptio 5.x and the identified PlatformInitAdvancedPreMem module. The bundle names a module GUID and SHA256, but does not enumerate specific OEM hardware models or firmware versions.
Exploitation context
The CVSS vector requires local access and high privileges, with no user interaction. KEV is false, and the source bundle contains no evidence of exploitation in the wild. Impact is serious because execution occurs before normal operating-system security controls.
Researcher notes
Key evidence is the named AMI Aptio 5.x module, GUID EEEE611D-F78F-4FB9-B868-55907F169280, and SHA256 644044fdb8daea30a7820e0f5f88dbf5cd460af72fbf70418e9d2e47efed8d9b. Validate exposure through firmware composition, not operating-system package checks.
Mitigation direction
- Check AMI, Intel, and OEM advisories for affected firmware and approved updates.
- Prioritize firmware updates for virtualization hosts and confidential-computing platforms.
- Restrict local administrative access on potentially affected systems.
- Track OEM firmware releases that address AMI Aptio 5.x PlatformInitAdvancedPreMem.
- Do not deploy unofficial firmware workarounds without vendor confirmation.
Validation and detection
- Inventory systems using AMI Aptio 5.x firmware.
- Compare firmware modules against the listed GUID and SHA256 where tooling permits.
- Check OEM advisories for affected models and fixed firmware versions.
- Verify firmware update status after remediation.
- Review high-value hosts for unauthorized firmware or boot-stage changes.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-121: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2022-26873 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 8.2 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H1.56Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
8.2HighVector: CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H
Source materials
- CVE List V5 sourceCVE List V5
- https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-00712.htmlCVE reference · x_refsource_MISC
- https://www.binarly.io/advisories/BRLY-2022-027CVE reference · x_refsource_MISC
- https://www.ami.com/security-center/CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Stack-based Buffer Overflow
Stack-based Buffer Overflow represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.