CVE-2026-67224: RabbitMQ path traversal in tracing plugin

CVE-2026-67224 · Severity: info · Published 2026-09-23

RabbitMQ is a message broker used by organizations to queue and route data between applications. An administrator with tracing plugin enabled can write log files with arbitrary names to any directory writable by the RabbitMQ system user, potentially overwriting critical files or achieving code execution. This requires active use of the tracing feature and administrative credentials, limiting exposure but enabling privilege escalation on compromised admin accounts.

Technologies: RabbitMQ. Vendors: RabbitMQ.

Quick answers

Is CVE-2026-67224 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-67224 being exploited in the wild.
How severe is CVE-2026-67224?
Informational severity, published 23 September 2026.
Which products and versions are affected?
RabbitMQ 3.13.0 to 3.13.14, 4.0.0 to 4.0.19, 4.1.0 to 4.1.10, 4.2.0 to 4.2.5, 4.3.0.
Is there a fix for CVE-2026-67224?
A patch was published on 2026-04-23: RabbitMQ 4.2.6 released Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-67224 attacked?
It is attacked over the network, in a hosted service.
Am I affected by CVE-2026-67224?
Check whether you run RabbitMQ at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

The vulnerability is a path traversal flaw in the rabbitmq_tracing plugin's trace consumer, which constructs output paths as filename:join(TraceDir, Name ++ ".log") without validating the Name parameter from PUT /api/traces/:vhost/:name for directory traversal. The read-side code properly calls rabbit_misc:safe_relative_path/1, confirming the omission is unintentional. An authenticated administrator can exploit this to write .log-suffixed files to arbitrary filesystem paths writable by the rabbitmq user (e.g., /etc/cron.d/x.log), achieving file write or overwrite primitives outside the intended trace directory.

Affected products

  • RabbitMQ RabbitMQ 3.13.0 to 3.13.14, 4.0.0 to 4.0.19, 4.1.0 to 4.1.10, 4.2.0 to 4.2.5, 4.3.0

Timeline

  • 2026-09-23: disclosed
  • 2026-04-23: patched: RabbitMQ 4.2.6 released
  • 2026-05-20: patched: RabbitMQ 4.3.1 released

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.