{"items":[{"id":"NVI-00015035","kind":"vulnerability","title":"RabbitMQ Java client accepts broker frames larger than the negotiated AMQP frame_max","revision":1,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-5xwg-cfvj-gff5","CVE-2026-61634"],"plain_summary":"GitHub lists this reviewed advisory for com.rabbitmq:amqp-client. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-0dc25510ab5befc02187ab8c06f4eb82"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-0dc25510ab5befc02187ab8c06f4eb82","url":"https://github.com/advisories/GHSA-5xwg-cfvj-gff5","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-5xwg-cfvj-gff5","publisher":"GitHub Advisory Database","observed_at":"2026-11-02T20:15:44.568Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-0dc25510ab5befc02187ab8c06f4eb82"],"technology":"com.rabbitmq:amqp-client","known_exclusions":[],"conditions_summary":"## Summary\nThe max body size was enforced to patch CVE-2023-46120, but even though that limit still works, the frame size itself still exceeds the given max size. \n\n## Root cause\nThe Java client records the AMQP 0-9-1 `frame_max` negotiated during connection tuning, but the socket inbound frame reader continues to validate broker-controlled payload lengths against the much larger `maxInboundMessageBodySize` limit. A broker peer can therefore send a method frame whose payload is larger than the negotiated `frame_max`, have it allocated and decoded, and complete the connection handshake instead of being rejected as a protocol violation.\n\n*Reported by Team Atlanta.*","public_affected_ranges":["< 5.33.0"]}],"null_published_at":"2026-11-03T10:03:26.538Z","source_updated_at":"2026-08-18T16:36:30.000Z","source_disclosed_at":"2026-08-18T16:36:29.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"First indexed by Null; source disclosure date is shown separately.","null_first_observed_at":"2026-11-02T20:15:44.568Z"}],"next_cursor":null,"snapshot_revision":"42594"}