LiveActive security incident?Get immediate response
CVE Record

CVE-2021-26387: Insufficient access controls in ASP kernel may allow a privileged attacker with access to AMD signing keys...

Insufficient access controls in ASP kernel may allow a privileged attacker with access to AMD signing keys and the BIOS menu or UEFI shell to map DRAM regions in protected areas, potentially leading to a loss of platform integrity.

LowCVSS 3.9Not KEV-listedUpdated
Glexia's TakeAutomated analysislow

Security readout for executives and security teams

Plain-English summary

This is a low-severity AMD platform firmware issue. An attacker would already need very high privileges, AMD signing-key access, and BIOS menu or UEFI shell access. If those conditions exist, protected memory regions could be mapped, which may weaken platform integrity.

Executive priority

Handle through normal firmware risk management, not emergency response, unless your environment has weak firmware access controls or sensitive AMD signing-key workflows.

Technical view

CVE-2021-26387 is CWE-863 insufficient access control in the AMD Secure Processor kernel. The CVSS 3.1 score is 3.9 with local access, high complexity, high privileges, changed scope, and limited integrity and availability impact. Affected products span multiple EPYC, Ryzen, Athlon, and Threadripper families.

Likely exposure

Exposure is most relevant to organizations operating affected AMD EPYC, Ryzen, Athlon, or Threadripper systems with vulnerable platform initialization or firmware versions. The practical attack path appears constrained by local, privileged, firmware-level access requirements.

Exploitation context

The provided bundle does not show CISA KEV listing or active exploitation evidence. Exploitation requires unusually strong prerequisites: privileged access, AMD signing keys, and BIOS menu or UEFI shell access.

Researcher notes

Evidence is limited to the CVE record and AMD advisory references. The affected list is broad, but exploitability is constrained by high privileges, local access, high complexity, and signing-key plus firmware-interface prerequisites.

Mitigation direction

  • Review AMD SB-3003 and SB-5002 for vendor firmware guidance.
  • Check OEM BIOS or UEFI update channels for affected systems.
  • Restrict BIOS menu and UEFI shell access to trusted administrators.
  • Protect firmware-signing material and related privileged workflows.
  • Prioritize servers or workstations with affected AMD processor families.

Validation and detection

  • Inventory AMD processor families across servers, desktops, and laptops.
  • Record BIOS, UEFI, AGESA, or PI firmware versions where available.
  • Compare inventory against affected products and versions in the CVE record.
  • Confirm firmware access controls limit BIOS menu and UEFI shell use.
  • Track AMD and OEM advisories for applicable remediation status.
Prepared
Confidence
high
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

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 · medium confidence lookup

CWE-863: Authorization and privilege behavior lookup

Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. 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 lookup
cve · low confidence lookup

CVE-2021-26387 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Low
CVSS
3.9 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:C/C:N/I:L/A:L

Official CVE source material

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.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We 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.

ScoreVersionSeverityVectorExploitImpactSource
3.9CVSS 3.1LowCVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:C/C:N/I:L/A:L0.82.7Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

3.9Low
CVSS 3.1 vector shape for CVE-2021-26387Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:C/C:N/I:L/A:L

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
AMDAMD EPYC™ 7001 Series ProcessorsPI, variousaffected
AMDAMD EPYC™ 7002 Series Processorsvariousaffected
AMDAMD EPYC™ 7003 Series Processorsvariousaffected
AMDAMD EPYC™ 9004 Series Processorsvariousaffected
AMDAMD Ryzen™ 3000 Series Desktop ProcessorsComboAM4PI 1.0.0.9, ComboAM4 V2 PI 1.2.0.8affected
AMDAMD Ryzen™ 5000 Series Desktop ProcessorsComboAM4 V2 PI 1.2.0.8affected
AMDAMD Ryzen™ 5000 Series Desktop Processor with Radeon™ GraphicsComboAM4v2 PI 1.2.0.6affected
AMDAMD Ryzen™ 7000 Series Desktop ProcessorsComboAM5 1.0.8.0affected
AMDAMD Athlon™ 3000 Series Desktop Processors with Radeon™ GraphicsComboAM4PI 1.0.0.9, ComboAM4v2 PI 1.2.0.8affected
AMDAMD Ryzen™ 4000 Series Desktop Processors with Radeon™ GraphicsComboAM4v2 PI 1.2.0.5affected
AMDAMD Ryzen™ Threadripper™ 3000 Series ProcessorsCastlePeakPI-SP3r3 1.0.0.7affected
AMDAMD Ryzen™ Threadripper™ PRO 3000WX Series ProcessorsChagallWSPI-sWRX8 1.0.0.2, CastlePeakWSPI-sWRX8 1.0.0.9affected
AMDAMD Ryzen™ Threadripper™ PRO 5000WX ProcessorsChagallWSPI-sWRX8 1.0.0.2affected
AMDAMD Athlon™ 3000 Series Mobile Processors with Radeon™ GraphicsPicassoPI-FP5 1.0.0.Eaffected
AMDAMD Athlon™ 3000 Series Mobile Processors with Radeon™ GraphicsPollockPI-FT5 1.0.0.4affected
AMDAMD Ryzen™ 3000 Series Mobile Processor with Radeon™ GraphicsPicassoPI-FP5 1.0.0.Eaffected
AMDAMD Ryzen™ 4000 Series Mobile Processors with Radeon™ GraphicsRenoirPI-FP6 1.0.0.8affected
AMDAMD Ryzen™ 5000 Series Mobile Processors with Radeon™ GraphicsCezannePI-FP6 1.0.0.9affected
AMDAMD Ryzen™ 5000 Series Mobile Processors with Radeon™ GraphicsCezannePI-FP6 1.0.0.9affected
AMDAMD Ryzen™ 6000 Series Processors with Radeon™ GraphicsRembrandtPI-FP7 1.0.0.9baffected
AMDAMD Ryzen™ 7035 Series Processors with Radeon™ GraphicsRembrandtPI-FP7 1.0.0.9baffected
AMDAMD Ryzen™ 5000 Series Processors with Radeon™ GraphicsCezannePI-FP6 1.0.0.9affected
AMDAMD Ryzen™ 3000 Series Processors with Radeon™ GraphicsCezannePI-FP6 1.0.0.9affected
AMDAMD EPYC™ Embedded 3000 Series Processorsvariousaffected
AMDAMD EPYC™ Embedded 7002 Series Processorsvariousaffected
AMDAMD EPYC™ Embedded 7003 Series Processorsvariousaffected
AMDAMD EPYC™ Embedded 9003 Series Processorsvariousaffected
AMDAMD Ryzen™ Embedded R1000 Series ProcessorsEmbeddedPI-FP5 1.2.0.Aaffected
AMDAMD Ryzen™ Embedded R2000 Series ProcessorsEmbeddedR2KPI-FP5 1.0.0.2affected
AMDAMD Ryzen™ Embedded 5000 Series ProcessorsEmbAM4PI 1.0.0.2affected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-863 · source CWE mapping

Incorrect Authorization

Incorrect Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.