LiveActive security incident?Get immediate response
CVE Record

CVE-2021-26407: A randomly generated Initialization Vector (IV) may lead to a collision of IVs with the same key potentiall...

A randomly generated Initialization Vector (IV) may lead to a collision of IVs with the same key potentially resulting in information disclosure.

MediumCVSS 5.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This AMD issue can expose information if encryption IVs randomly collide while using the same key. The public record ties it to AMD 2nd Gen EPYC AGESA variants. It is not described as remotely exploitable and requires local privileges, so urgency depends on where these processors support sensitive workloads.

Executive priority

Treat this as a confidentiality-focused firmware risk, not an emergency from the available evidence. Prioritize verification and remediation for sensitive or multi-tenant servers, then fold remaining updates into normal firmware maintenance windows.

Technical view

CVE-2021-26407 is a CWE-330 weakness involving randomly generated IVs that may collide under the same key, potentially causing confidentiality impact. The CVSS 3.1 vector is local, low complexity, low privileges, no user interaction, unchanged scope, high confidentiality impact only.

Likely exposure

Likely exposure is systems using AMD 2nd Gen EPYC with affected AGESA firmware versions. The bundle says versions are various and default status is unaffected, so asset owners must confirm specific platform firmware status through AMD and OEM guidance.

Exploitation context

The provided sources do not show active exploitation, and CISA KEV status is false. The CVSS vector indicates an attacker needs local low-privileged access. Public evidence does not provide exploit mechanics or real-world incident context.

Researcher notes

The source bundle gives limited technical detail beyond IV collision risk and CVSS scoring. Do not assume affected firmware versions, exploitation, or fixes beyond AMD-SB-1032 and OEM guidance. The main validation work is firmware and platform correlation.

Mitigation direction

  • Review AMD-SB-1032 and the relevant OEM platform advisory.
  • Update BIOS or firmware if AMD or the OEM identifies the platform as affected.
  • Prioritize shared, virtualized, or sensitive-data hosts during firmware planning.
  • Track exceptions where OEM firmware is unavailable or unsupported.

Validation and detection

  • Inventory AMD 2nd Gen EPYC systems and record BIOS or AGESA versions.
  • Compare installed firmware against AMD-SB-1032 and OEM release notes.
  • Confirm firmware updates completed successfully through management tooling.
  • Document unaffected systems with evidence from vendor or OEM guidance.
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-330: 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-26407 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
Medium
CVSS
5.5 (3.1)
Known Exploited
No
Published

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

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
5.5CVSS 3.1MediumCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N1.83.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.5Medium
CVSS 3.1 vector shape for CVE-2021-26407Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

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
AMD2nd 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-330 · source CWE mapping

Use of Insufficiently Random Values

Use of Insufficiently Random Values represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.