Connect your agent
AdvisoriesCriticalCheck your lockfilePluginHow it worksPricing Connect your agent

Advisory record · GHSA-cqgh-8p3p-mx4m

RabbitMQ: JSONReader in the default JSON-RPC mapper never terminates on truncated input, causing DoS

CVSS 4.9 MediumEPSS 0.0053 · 45th percentile

Published by the GitHub Advisory Database at 7 Oct 2026, 20:42 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
com.rabbitmq:amqp-clientMaven<5.36.15.36.1
Identifiers
GHSA-cqgh-8p3p-mx4m · CVE-2026-106121
Weakness (CWE)
CWE-835
Tags
Published
7 Oct 2026
Updated
7 Oct 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

The amqp-client Maven package, versions before 5.36.1, has a flaw in its JSON-RPC tooling where the JSONReader parser never terminates on input that ends inside a quoted string or a line comment. An attacker who can send a single message to a JSON-RPC server's request queue, or who controls a JSON-RPC service a client talks to, can hang the endpoint: an unterminated string exhausts the heap, and an unterminated comment pins a thread at full CPU. Upgrade to amqp-client 5.36.1 or later. Applications that supply their own mapper instead of the default DefaultJsonRpcMapper are not affected.

Written 2 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
4.9 Medium 3.1 CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0053, the 45th percentile, on 5 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:16 UTC First seen by agentprime
  2. 31 Oct 2026, 14:16 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.