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 75% 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

A fix is available — apply it.

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
25%
KEV
Not listed

Published

August 26, 2026

Last Modified

September 9, 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

Vendor Advisories for CVE-2026-79921(3)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(2)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatcustom-metrics-autoscaler/custom-metrics-autoscaler-rhel9-operator:17882901212026-09-02redhat
redhatopentelemetry-collector-contrib-main-0.159.0-0.1.1.hum12026-08-29redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(4 across 4 ecosystems)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
golang-github-rabbitmq-amqp091-go1.10.0-1 ... 1.9.0-1 (8 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
golang-github-rabbitmq-amqp091-go1.10.0-1, 1.11.0-1, 1.12.0-1, 1.14.0-1——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
golang-github-rabbitmq-amqp091-go1.10.0-1, 1.11.0-1, 1.12.0-11.14.0-1—
Go(1)
PackageVulnerable rangeFixed inDependents
github.com/rabbitmq/amqp091-go—1.13.0—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 26× in last 7d / 73× 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-09-19 10:02 UTCVendor advisory
  2. 2026-09-18 21:31 UTCEG score recompute
  3. 2026-09-18 21:31 UTCVendor advisory
  4. 2026-09-18 19:28 UTCEPSS rescore
  5. 2026-09-18 08:47 UTCVendor advisory
  6. 2026-09-17 20:57 UTCEG score recompute
  7. 2026-09-17 20:57 UTCVendor advisory
  8. 2026-09-17 06:56 UTCVendor advisory
  9. 2026-09-16 19:06 UTCEG score recompute
  10. 2026-09-16 19:06 UTCVendor advisory
  11. 2026-09-16 14:08 UTCEPSS rescore
  12. 2026-09-16 07:04 UTCEG score recompute
  13. 2026-09-16 07:04 UTCVendor advisory
  14. 2026-09-16 05:15 UTCEPSS rescore
  15. 2026-09-15 19:15 UTCVendor advisory
  16. 2026-09-15 07:25 UTCEG score recompute
  17. 2026-09-15 07:25 UTCVendor advisory
  18. 2026-09-15 03:12 UTCEPSS rescore
  19. 2026-09-15 03:12 UTCEPSS rescore
  20. 2026-09-14 19:35 UTCVendor advisory
  21. 2026-09-14 07:45 UTCVendor advisory
  22. 2026-09-13 19:55 UTCEG score recompute
  23. 2026-09-13 19:55 UTCVendor advisory
  24. 2026-09-13 08:05 UTCVendor advisory
  25. 2026-09-12 20:15 UTCEG score recompute
Show 48 more
  1. 2026-09-12 20:15 UTCVendor advisory
  2. 2026-09-12 08:25 UTCVendor advisory
  3. 2026-09-11 20:35 UTCEG score recompute
  4. 2026-09-11 20:35 UTCVendor advisory
  5. 2026-09-11 14:53 UTCEPSS rescore
  6. 2026-09-11 14:53 UTCEPSS rescore
  7. 2026-09-11 08:44 UTCVendor advisory
  8. 2026-09-10 20:54 UTCEG score recompute
  9. 2026-09-10 20:54 UTCVendor advisory
  10. 2026-09-10 09:03 UTCVendor advisory
  11. 2026-09-09 21:12 UTCVendor advisory
  12. 2026-09-09 12:46 UTCVendor advisory
  13. 2026-09-09 00:47 UTCEG score recompute
  14. 2026-09-09 00:47 UTCVendor advisory
  15. 2026-09-08 22:01 UTCEPSS rescore
  16. 2026-09-08 02:59 UTCEG score recompute
  17. 2026-09-08 02:59 UTCVendor advisory
  18. 2026-09-07 15:09 UTCVendor advisory
  19. 2026-09-07 00:36 UTCEG score recompute
  20. 2026-09-07 00:36 UTCVendor advisory
  21. 2026-09-06 13:48 UTCEPSS rescore
  22. 2026-09-06 12:46 UTCVendor advisory
  23. 2026-09-06 00:57 UTCVendor advisory
  24. 2026-09-05 13:03 UTCVendor advisory
  25. 2026-09-05 01:12 UTCEG score recompute
  26. 2026-09-05 01:12 UTCVendor advisory
  27. 2026-09-04 13:20 UTCEG score recompute
  28. 2026-09-04 05:07 UTCEPSS rescore
  29. 2026-09-03 01:48 UTCEG score recompute
  30. 2026-09-02 14:12 UTCEPSS rescore
  31. 2026-09-01 14:14 UTCEG score recompute
  32. 2026-09-01 13:54 UTCEPSS rescore
  33. 2026-09-01 04:40 UTCEPSS rescore
  34. 2026-09-01 04:40 UTCEPSS rescore
  35. 2026-08-31 02:44 UTCEG score recompute
  36. 2026-08-30 19:18 UTCEPSS rescore
  37. 2026-08-30 19:17 UTCEPSS rescore
  38. 2026-08-30 03:02 UTCEG score recompute
  39. 2026-08-30 01:22 UTCEPSS rescore
  40. 2026-08-29 03:23 UTCEG score recompute
  41. 2026-08-29 03:02 UTCEG score recompute
  42. 2026-08-28 23:57 UTCEG score recompute
  43. 2026-08-28 21:42 UTCEPSS rescore
  44. 2026-08-27 21:06 UTCEG score recompute
  45. 2026-08-27 14:25 UTCEPSS rescore
  46. 2026-08-26 21:25 UTCEG score recompute
  47. 2026-08-26 21:02 UTCEG score recompute
  48. 2026-08-26 21:01 UTCMITRE cvelistV5first tracked

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 September 9, 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 75.2% 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

See which npm, PyPI, Go, and Maven packages are affected by 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