---
id: CVE-2026-67415
title: RabbitMQ is a messaging and streaming broker
summary: >-
  RabbitMQ is a messaging and streaming broker. From 4.2.0 until 4.2.9 and
  4.3.3, the Shovel parameter parser converted attacker-controlled runtime
  parameter values into non-garbage-collected Erlang atoms before bounding them
  or checking a…
severity: medium
cvss: 5.9
cvssVector: 'CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N'
cwe:
  - CWE-400
vendor: rabbitmq
product: rabbitmq-server
affected:
  - 'rabbitmq-server >= 4.3.0, < 4.3.3'
  - 'rabbitmq-server >= 4.2.0, < 4.2.9'
published: '2026-09-25'
updated: '2026-09-25'
sourceUpdated: '2026-09-25T20:17:39.433'
source: NVD
sourceUrl: 'https://nvd.nist.gov/vuln/detail/CVE-2026-67415'
references:
  - url: 'https://github.com/rabbitmq/rabbitmq-server/releases/tag/v4.2.9'
    label: security-advisories@github.com
  - url: 'https://github.com/rabbitmq/rabbitmq-server/releases/tag/v4.3.3'
    label: security-advisories@github.com
  - url: >-
      https://github.com/rabbitmq/rabbitmq-server/security/advisories/GHSA-8mpg-qw9r-m5cr
    label: security-advisories@github.com
  - url: >-
      https://github.com/rabbitmq/rabbitmq-server/security/advisories/GHSA-8mpg-qw9r-m5cr
    label: 134c704f-9b21-4f2e-91b3-4a467353bcc0
tags:
  - nvd
  - cve.org
  - exploit-available
exploitAvailable: true
ssvc:
  exploitation: poc
  automatable: 'no'
  technicalImpact: partial
  timestamp: '2026-09-25T19:59:31.171216Z'
cvssSource: cna
ingestedAt: '2026-09-25T17:13:14.024Z'
---

## Overview

RabbitMQ is a messaging and streaming broker. From 4.2.0 until 4.2.9 and 4.3.3, the Shovel parameter parser converted attacker-controlled runtime parameter values into non-garbage-collected Erlang atoms before bounding them or checking a fixed allowlist. Exploitation requires network access to the Management HTTP API, valid credentials with both the management and policymaker tags, permission to set Shovel runtime parameters on a vhost, and the rabbitmq_shovel and rabbitmq_shovel_management plugins to be enabled. The attacker can exhaust the node-wide atom table and deny service, and malicious parameters are stored durably and reparsed when workers start, so atom pressure can recur after restart without a live attacker connection. This issue is fixed in versions 4.2.9 and 4.3.3.

## Remediation

Refer to the linked advisories for vendor-supplied fixes and affected version ranges.