Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 8.7amended

RabbitMQ Java client has frame-level OOM: Math.min(maxInboundMessageBodySize, 0) defeats frame size enforcement

CVE-2026-75516GHSA-jh4v-gfqj-7rhx

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (com.rabbitmq:amqp-client 5.34.0), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
8.7 · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N · score source
EPSS
  • CVE-2026-75516: 0.55% estimated exploitation activity in the next 30 days; percentile 46.19 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Vulnerability In AMQConnection.java (line 435-436), after Connection.Tune negotiation, the frame-max limit is set via: When frameMax = 0 (meaning "unlimited" per AMQP spec), Math.min(67108864, 0) = 0. This value is then passed to Utils.framePayloadLimit(0) which returns Integer.MAXVALUE (line 77-79 of Utils.java): This completely defeats the maxInboundMessageBodySize protection (default 64MB) at the frame level. Attack Scenario A malicious AMQP server (or MITM) sends Connection.Tune with frameMax=0: 1. Client defaults: requestedFrameMax = 0 (ConnectionFactory.DEFAULTFRAMEMAX, line 82) 2. negotiatedMaxValue(0, 0) = Math.max(0, 0) = 0 (line 673-676) 3. Math.min(maxInboundMessageBodySize, 0) = 0 — 64MB cap defeated 4. framePayloadLimit(0) = Integer.MAXVALUE — no frame size enforcement 5. Attacker sends a single frame with frameSize = 0x1FFFFFFF (~500MB) 6. Frame.readFrom() (line 135) executes new byte[frameSize] — OOM crash The frame does not need to be a body frame — method frames,…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 3 · amended ·

    Amended from ghsa record GHSA-jh4v-gfqj-7rhx

  2. Revision 2 · amended ·

    Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

  3. Revision 1 · created ·

    Published from osv record GHSA-jh4v-gfqj-7rhx

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-75516

Advisory: RabbitMQ Java client has frame-level OOM: Math.min(maxInboundMessageBodySize, 0) defeats frame size enforcement
IDs: CVE-2026-75516, GHSA-jh4v-gfqj-7rhx
Record: https://patchnext.com/advisories/cve-2026-75516 (revision 3, source checked 26 Oct 2026, 16:55 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.7)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: com.rabbitmq:amqp-client 5.34.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven com.rabbitmq:amqp-client: affected < 5.34.0; fixed in 5.34.0

## Suggested inspection (read-only)
- Maven com.rabbitmq:amqp-client: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on com.rabbitmq:amqp-client.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-jh4v-gfqj-7rhx (OSV record GHSA-jh4v-gfqj-7rhx lists affected ranges: Maven com.rabbitmq:amqp-client >=0 <5.34.0 (fixed))
- Verified: https://github.com/advisories/GHSA-jh4v-gfqj-7rhx (GitHub-reviewed advisory GHSA-jh4v-gfqj-7rhx lists affected ranges: Maven com.rabbitmq:amqp-client >=0 <5.34.0)

Commands are suggestions: review each one before running it.

Loading voting…