LiveActive security incident?Get immediate response
CVE Record

CVE-2021-26409: Insufficient bounds checking in SEV-ES may allow an attacker to corrupt Reverse Map table (RMP) memory, pot...

Insufficient bounds checking in SEV-ES may allow an attacker to corrupt Reverse Map table (RMP) memory, potentially resulting in a loss of SNP (Secure Nested Paging) memory integrity.

HighCVSS 7.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

This AMD processor firmware issue can undermine memory-integrity protections used for confidential computing. An attacker with local, low-privileged access could potentially corrupt RMP memory, affecting SNP protection guarantees on impacted 3rd Gen EPYC systems.

Executive priority

Treat as high priority for confidential-computing or multi-tenant virtualization environments using AMD 3rd Gen EPYC. For standard workloads without SEV-ES or SNP exposure, urgency is lower but firmware status should still be tracked.

Technical view

CVE-2021-26409 is an insufficient bounds-checking flaw in AMD SEV-ES involving RMP memory. The reported impact is potential loss of Secure Nested Paging memory integrity. CVSS 3.1 is 7.8, local attack vector, low complexity, low privileges, no user interaction, with high confidentiality, integrity, and availability impact.

Likely exposure

Exposure is most relevant to environments running AMD 3rd Gen EPYC platforms with SEV-ES or SNP-dependent confidential-computing workloads. The source bundle does not identify exact AGESA versions or OEM firmware levels.

Exploitation context

The source bundle does not report active exploitation, and the CVE is not marked KEV. The CVSS vector indicates exploitation requires local access and low privileges, not network-only access.

Researcher notes

The public bundle gives the impact class and CVSS vector but not exact vulnerable AGESA builds, patch levels, or a proof-of-concept status. Analysis should remain anchored to AMD-SB-1032 and OEM firmware documentation.

Mitigation direction

  • Review AMD-SB-1032 for official affected-version and remediation details.
  • Check server OEM firmware advisories for applicable AGESA updates.
  • Inventory 3rd Gen EPYC hosts using SEV-ES or SNP features.
  • Limit local access to affected virtualization hosts.
  • Avoid placing sensitive SNP-dependent workloads on unverified firmware baselines.

Validation and detection

  • Identify AMD 3rd Gen EPYC systems in asset inventory.
  • Record BIOS, firmware, and AGESA versions from each platform.
  • Compare platform firmware status against AMD and OEM guidance.
  • Confirm whether SEV-ES or SNP is enabled for workloads.
  • Document systems where vendor remediation status remains unclear.
Prepared
Confidence
medium
Sources
3

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

CWE-120: 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 lookup
cve · low confidence lookup

CVE-2021-26409 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
High
CVSS
7.8 (3.1)
Known Exploited
No
Published

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

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
2Source 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
7.8CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.8High
CVSS 3.1 vector shape for CVE-2021-26409Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

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

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
AMD3rd Gen EPYCAGESA, variousunaffected
Weakness

CWE details

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

CWE-120 · source CWE mapping

Buffer Copy without Checking Size of Input ('Classic Buffer Overflow')

Buffer Copy without Checking Size of Input ('Classic Buffer Overflow') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.