CVE-2026-75516

HIGHPre-NVD 8.78.7—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.7 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5%, top 56% 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.7EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 8.7Exploit: None knownExposed: 0

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

The RabbitMQ Java client library allows Java and JVM-based applications to connect to and interact with RabbitMQ nodes. Prior to 5.34.0, AMQConnection.start() applies Math.min(maxInboundMessageBodySize, frameMax) after Connection.Tune negotiation even though AMQP defines frameMax value zero as unlimited and ConnectionFactory.DEFAULT_FRAME_MAX is zero. When the client default and server-negotiated value are both zero, the result is passed to Utils.framePayloadLimit(int), which interprets zero as Integer.MAX_VALUE and disables the configured maxInboundMessageBodySize cap. A malicious AMQP server, or a man-in-the-middle attacker able to modify Connection.Tune and inject frames into the connection, can then send an oversized frame of any frame type, causing Frame.readFrom() to allocate a large byte array before content-level validation and potentially terminate the client process through memory exhaustion. This issue is fixed in version 5.34.0.

CVSS v3
8.7
EG Score
8.7(medium)
EG Risk
54(Track)
EG Risk 54/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
Severity87% × 45%
Exploitation1% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
44%
KEV
Not listed

Published

September 16, 2026

Last Modified

September 18, 2026

Advisory Details (6)

Auto-updated Sep 16, 2026
Patch available. Sources: github_release, github, github_pr, github_commit.
github_release Patch Available

5.34.0

Patch available: rabbitmq/rabbitmq-java-client v5.34.0

https://github.com/rabbitmq/rabbitmq-java-client/releases/tag/v5.34.0
github_commit Patch Available

commit e7f10bf99aee (rabbitmq/rabbitmq-java-client)

Patch available: rabbitmq/rabbitmq-java-client v5.34.0 (contains commit e7f10bf99aee)

https://github.com/rabbitmq/rabbitmq-java-client/commit/e7f10bf99aee103dd9f64b3e52a725fc9f9d3763
github_commit

commit 6d7c2bfe8979 (rabbitmq/rabbitmq-java-client)

Fix landed in rabbitmq/rabbitmq-java-client commit 6d7c2bfe8979 — awaiting tagged release

https://github.com/rabbitmq/rabbitmq-java-client/commit/6d7c2bfe89796ca34d3531098fb59dd657fea39e
github_pr Patch Available

Honor unlimited negotiated frame_max when capping inbound message size (backport #2015)

Patch available: rabbitmq/rabbitmq-java-client v5.34.0 (PR #2016 merged 2026-07-08)

https://github.com/rabbitmq/rabbitmq-java-client/pull/2016
github_pr

Honor unlimited negotiated frame_max when capping inbound message size

Fix merged in rabbitmq/rabbitmq-java-client PR #2015 on 2026-07-08 — awaiting tagged release

https://github.com/rabbitmq/rabbitmq-java-client/pull/2015
github Patch Available

Frame-level OOM: Math.min(maxInboundMessageBodySize, 0) defeats frame size enforcement · Advisory · rabbitmq/rabbitmq-java-client · GitHub

https://github.com/rabbitmq/rabbitmq-java-client/security/advisories/GHSA-jh4v-gfqj-7rhx

Vendor Advisories for CVE-2026-75516(1)

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

Affected Packages

(1 across 1 ecosystem)
Maven(1)
PackageVulnerable rangeFixed inDependents
com.rabbitmq:amqp-client1.3.0 ... 5.9.0 (152 versions)5.34.0—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 8× in last 7d / 8× 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 06:35 UTCEG score recompute
  2. 2026-09-18 19:28 UTCEPSS rescore
  3. 2026-09-18 19:28 UTCEG score recompute
  4. 2026-09-18 18:34 UTCEG score recompute
  5. 2026-09-18 05:25 UTCEG score recompute
  6. 2026-09-16 19:24 UTCEG score recompute
  7. 2026-09-16 18:40 UTCEG score recompute
  8. 2026-09-16 18:39 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-75516?
CVE-2026-75516 is a high vulnerability published on September 16, 2026. The RabbitMQ Java client library allows Java and JVM-based applications to connect to and interact with RabbitMQ nodes. Prior to 5.34.0, AMQConnection.start() applies Math.min(maxInboundMessageBodySize, frameMax) after Connection.Tune negotiation even though AMQP defines frameMax value zero as…
When was CVE-2026-75516 disclosed?
CVE-2026-75516 was first published in the National Vulnerability Database on September 16, 2026, with the most recent update on September 18, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-75516 actively exploited?
CVE-2026-75516 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 56.3% of all scored CVEs.
What is the CVSS score of CVE-2026-75516?
CVE-2026-75516 has a CVSS v3 base score of 8.7 (NVD).
How do I remediate CVE-2026-75516?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-75516, 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-75516

Explore →

Is Your Infrastructure Affected by CVE-2026-75516?

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

Start Free Scan →Browse All CVEs