CVE-2026-67224: CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') in rabbitmq rabbitmq-server
RabbitMQ is a messaging and streaming broker. Prior to versions 3.13.15, 4.0.20, 4.1.11, 4.2.6, and 4.3.1, The trace consumer constructs the output path as filename:join(TraceDir, Name ++ ".log") where Name comes from PUT /api/traces/:vhost/:name. No safe_relative_path / traversal check is applied on the write side, while the read side (rabbit_tracing_files.erl) does call rabbit_misc:safe_relative_path/1 , proving the omission is an oversight, not design. The .log suffix is forced and the endpoint requires administrator. A user with the administrator tag can write a .log-suffixed file to an arbitrary filesystem path writable by the rabbitmq user via the tracing plugin's name parameter, e.g. /etc/cron.d/x.log (if writable) or overwrite existing .log files outside the trace directory. Preconditions include rabbitmq_tracing plugin enabled administrator tag Target path writable by rabbitmq OS user. This issue is fixed in versions 3.13.15, 4.0.20, 4.1.11, 4.2.6, and 4.3.1.
AI Analysis
Technical Summary
RabbitMQ's trace consumer constructs output paths for trace logs by joining a trace directory with a user-supplied name plus a ".log" suffix. However, it lacks a safe relative path or traversal check on the write side, unlike the read side which performs such validation. This oversight allows an administrator user with the rabbitmq_tracing plugin enabled to write .log files to arbitrary filesystem locations writable by the rabbitmq OS user, potentially overwriting files outside the trace directory. The vulnerability affects rabbitmq-server versions prior to 3.13.15, 4.0.20, 4.1.11, 4.2.6, and 4.3.1 and is fixed in those versions.
Potential Impact
An attacker with administrator privileges and the tracing plugin enabled can write or overwrite .log files at arbitrary filesystem paths writable by the rabbitmq user. This could lead to unauthorized file modification outside the intended trace directory. The CVSS score is low (2.1), reflecting the requirement for high privileges and limited impact scope.
Mitigation Recommendations
Upgrade rabbitmq-server to versions 3.13.15, 4.0.20, 4.1.11, 4.2.6, or 4.3.1 or later where this vulnerability is fixed. Ensure that only trusted users have administrator privileges and that the rabbitmq_tracing plugin is enabled only when necessary. No additional mitigation is required once patched.
CVE-2026-67224: CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') in rabbitmq rabbitmq-server
Description
RabbitMQ is a messaging and streaming broker. Prior to versions 3.13.15, 4.0.20, 4.1.11, 4.2.6, and 4.3.1, The trace consumer constructs the output path as filename:join(TraceDir, Name ++ ".log") where Name comes from PUT /api/traces/:vhost/:name. No safe_relative_path / traversal check is applied on the write side, while the read side (rabbit_tracing_files.erl) does call rabbit_misc:safe_relative_path/1 , proving the omission is an oversight, not design. The .log suffix is forced and the endpoint requires administrator. A user with the administrator tag can write a .log-suffixed file to an arbitrary filesystem path writable by the rabbitmq user via the tracing plugin's name parameter, e.g. /etc/cron.d/x.log (if writable) or overwrite existing .log files outside the trace directory. Preconditions include rabbitmq_tracing plugin enabled administrator tag Target path writable by rabbitmq OS user. This issue is fixed in versions 3.13.15, 4.0.20, 4.1.11, 4.2.6, and 4.3.1.
CVSS v4.0
Score 2.1low
Affected software
rabbitmq
rabbitmq-server
pkg:github/rabbitmq/rabbitmq-serverRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
RabbitMQ's trace consumer constructs output paths for trace logs by joining a trace directory with a user-supplied name plus a ".log" suffix. However, it lacks a safe relative path or traversal check on the write side, unlike the read side which performs such validation. This oversight allows an administrator user with the rabbitmq_tracing plugin enabled to write .log files to arbitrary filesystem locations writable by the rabbitmq OS user, potentially overwriting files outside the trace directory. The vulnerability affects rabbitmq-server versions prior to 3.13.15, 4.0.20, 4.1.11, 4.2.6, and 4.3.1 and is fixed in those versions.
Potential Impact
An attacker with administrator privileges and the tracing plugin enabled can write or overwrite .log files at arbitrary filesystem paths writable by the rabbitmq user. This could lead to unauthorized file modification outside the intended trace directory. The CVSS score is low (2.1), reflecting the requirement for high privileges and limited impact scope.
Mitigation Recommendations
Upgrade rabbitmq-server to versions 3.13.15, 4.0.20, 4.1.11, 4.2.6, or 4.3.1 or later where this vulnerability is fixed. Ensure that only trusted users have administrator privileges and that the rabbitmq_tracing plugin is enabled only when necessary. No additional mitigation is required once patched.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-07-28T19:50:39.437Z
- Cvss Version
- 4.0
- State
- PUBLISHED
Threat ID: 6ab43797f7a7c541064a9656
Added to database: 09/23/2026, 20:33:27 UTC
Last enriched: 09/23/2026, 20:48:11 UTC
Last updated: 09/24/2026, 01:57:04 UTC
Views: 8
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.