{"id":"CVE-2026-67224","title":"RabbitMQ is a messaging and streaming broker","summary":"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/:vh…","severity":"low","cvss":2.1,"cvssVector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N","cwe":["CWE-22"],"vendor":"rabbitmq","product":"rabbitmq-server","affected":["rabbitmq-server >= 3.13.0, < 3.13.15","rabbitmq-server >= 4.0.0, < 4.0.20","rabbitmq-server >= 4.1.0, < 4.1.11","rabbitmq-server >= 4.2.0, < 4.2.6","rabbitmq-server >= 4.3.0, < 4.3.1"],"published":"2026-09-23","updated":"2026-09-24","sourceUpdated":"2026-09-24T16:17:09.280","source":"NVD","sourceUrl":"https://nvd.nist.gov/vuln/detail/CVE-2026-67224","references":[{"url":"https://github.com/rabbitmq/rabbitmq-server/releases/tag/v4.2.6","label":"security-advisories@github.com"},{"url":"https://github.com/rabbitmq/rabbitmq-server/releases/tag/v4.3.1","label":"security-advisories@github.com"},{"url":"https://github.com/rabbitmq/rabbitmq-server/security/advisories/GHSA-h7cq-qrr8-7vgc","label":"security-advisories@github.com"},{"url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-67224.json"},{"url":"https://access.redhat.com/security/cve/CVE-2026-67224"},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2539762"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-67224"},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-67224"}],"tags":["nvd","cve.org","csaf","vex","red-hat","score-dispute"],"ssvc":{"exploitation":"none","automatable":"no","technicalImpact":"partial","timestamp":"2026-09-24T15:19:57.876579Z"},"cvssSource":"cna","scores":{"cna":2.1,"vendor":6.5},"ingestedAt":"2026-09-23T20:32:10.759Z","slug":"CVE-2026-67224","body":"## Overview\n\nRabbitMQ 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.\n\n## Remediation\n\nRefer to the linked advisories for vendor-supplied fixes and affected version ranges.\n\n## Vendor advisories\n\n- **Red Hat VEX** · Moderate · affected: Red Hat Hardened Images · no fix planned: Red Hat Hardened Images · updated 2026-09-24 · [vex](https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-67224.json)","depth":"sunlit","depthScore":12,"depthScoreParts":{"impact":11.6,"likelihood":0,"exploitation":0,"ransomware":0},"changes":[]}