RabbitMQ: Atom exhaustion: OAuth2 JWT tag: scope values

Versions reported by the vendor

Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.

• rabbitmq rabbitmq-server

  • >= 3.13.0, < 3.13.15, >= 4.0.0, < 4.0.22, >= 4.1.0, < 4.1.11, >= 4.2.0, < 4.2.6, >= 4.3.0, < 4.3.1affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

Other highest-scoring records for the same primary product.

• CVE-2026-67404RabbitMQ: OAuth2 silent verify_none fallback for JWKS fetch
  36Monitor
• CVE-2026-67231RabbitMQ: Trust-store whitelist by Issuer+Serial only
  36Monitor
• CVE-2026-67410RabbitMQ: OAuth2 Client Secret Exposed via Unauthenticated JavaScript Endpoint
  32Monitor
• CVE-2026-67409RabbitMQ: JWKS Fetch Ignores HTTP Response Status Code - Signing Key Destruction Causes Authentication DoS
  32Monitor
• CVE-2026-67236RabbitMQ: Plaintext username:password stored in an insecure cookie after successful POST /login
  32Monitor
• CVE-2026-66079RabbitMQ: Pre-auth AMQP 1.0 array32 zero-width element DoS
  32Monitor

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Root cause

Code that parses nested structures sets no depth or size limit. A small input can turn into a disproportionate processing load.

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

1function expand(node) {2  return node.children.map(expand);3}

1const MAX_DEPTH = 32;2function expand(node, depth = 0) {3  if (depth > MAX_DEPTH) throw new Error("too deep");4  return node.children.map((c) => expand(c, depth + 1));5}

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.