CVE-2026-79921

HIGHPre-NVD 8.98.9—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.9 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 76% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 3 sources updated this week
8.9EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.9Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

amqp091-go is a Go AMQP 0.9.1 client. Before version 1.13.0, a compromised or malicious AMQP broker can force the client to allocate resources for and process content body frames that exceed the negotiated frame_max limit. This can lead to unexpected memory consumption or application-layer denial of service (DoS), bypassing the protocol's built-in framing constraints. Version 1.13.0 contains a fix. No known workarounds are available.

CVSS v3
8.9
EG Score
8.9(medium)
EG Risk
55(Track)
EG Risk 55/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity89% × 45%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
24%
KEV
Not listed

Published

August 26, 2026

Last Modified

August 29, 2026

Advisory Details (4)

Auto-updated Aug 26, 2026
Patch available. Sources: github_commit, github_release, github, github_pr.
github_release Patch Available

v1.13.0

Patch available: rabbitmq/amqp091-go v1.13.0

https://github.com/rabbitmq/amqp091-go/releases/tag/v1.13.0
github_commit Patch Available

commit 6beb7b51f59e (rabbitmq/amqp091-go)

Patch available: rabbitmq/amqp091-go v1.13.0 (contains commit 6beb7b51f59e)

https://github.com/rabbitmq/amqp091-go/commit/6beb7b51f59e46ddcf8066ad498dad32491d3be0
github_pr Patch Available

fix: enforce AMQP minimum frame size during negotiation

Patch available: rabbitmq/amqp091-go v1.13.0 (PR #353 merged 2026-06-19)

https://github.com/rabbitmq/amqp091-go/pull/353
github Patch Available

Potential Memory Exhaustion/Protocol Violation via Broker-Controlled Oversized Payload in amqp091-go · Advisory · rabbitmq/amqp091-go · GitHub

https://github.com/rabbitmq/amqp091-go/security/advisories/GHSA-6c5v-hqjr-5xxp

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 11× in last 7d / 11× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-30 03:02 UTCEG score recompute
  2. 2026-08-30 01:22 UTCEPSS rescore
  3. 2026-08-29 03:23 UTCEG score recompute
  4. 2026-08-29 03:02 UTCEG score recompute
  5. 2026-08-28 23:57 UTCEG score recompute
  6. 2026-08-28 21:42 UTCEPSS rescore
  7. 2026-08-27 21:06 UTCEG score recompute
  8. 2026-08-27 14:25 UTCEPSS rescore
  9. 2026-08-26 21:25 UTCEG score recompute
  10. 2026-08-26 21:02 UTCEG score recompute
  11. 2026-08-26 21:01 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-79921?
CVE-2026-79921 is a high vulnerability published on August 26, 2026. amqp091-go is a Go AMQP 0.9.1 client. Before version 1.13.0, a compromised or malicious AMQP broker can force the client to allocate resources for and process content body frames that exceed the negotiated frame_max limit. This can lead to unexpected memory consumption or application-layer denial…
When was CVE-2026-79921 disclosed?
CVE-2026-79921 was first published in the National Vulnerability Database on August 26, 2026, with the most recent update on August 29, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-79921 actively exploited?
CVE-2026-79921 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 76.1% of all scored CVEs.
What is the CVSS score of CVE-2026-79921?
CVE-2026-79921 has a CVSS v3 base score of 8.9 (NVD).
How do I remediate CVE-2026-79921?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-79921, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-79921

Explore →

Is Your Infrastructure Affected by CVE-2026-79921?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs