Skip to content
Heist/ feed
Back to feed
Low

RabbitMQ: Admin path-traversal write via trace name

Type: advisorySources: OSV

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.

Products
Not specified
Affected versions
Not specified
Fixed versions
Not specified
CVEs
CVE-2026-67224
Confirmed fixed CVEs
Not specified
Updated in this feed
4 Nov 2026, 13:16 UTC · Revision 1

Source evidence

RabbitMQ: Admin path-traversal write via trace name

core-osv · Original source

Published 23 Sept 2026, 20:05 UTC

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.

osv:CVE-2026-67224
Complete source record
{
  "id": "6663008539ca86d20d3b9868a047fff91503e9c22605163104d2aca96a48ca94",
  "url": "https://osv.dev/vulnerability/CVE-2026-67224",
  "method": "structured",
  "payload": {
    "kind": "advisory",
    "title": "RabbitMQ: Admin path-traversal write via trace name",
    "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/: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.",
    "evidence": "osv:CVE-2026-67224",
    "products": [],
    "severity": "low",
    "structured": {
      "id": "CVE-2026-67224",
      "aliases": [
        "BIT-rabbitmq-2026-67224",
        "CVE-2026-67224",
        "GHSA-h7cq-qrr8-7vgc"
      ],
      "metrics": [
        {
          "type": "CVSS_V4",
          "score": "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"
        }
      ],
      "affected": [
        {
          "ranges": [
            {
              "repo": "https://github.com/rabbitmq/rabbitmq-server",
              "type": "GIT",
              "events": [
                {
                  "introduced": "95c501fbad76c66156346cf364d158d6e30aa4d9"
                },
                {
                  "fixed": "8a56c37f099a7bf609a555de3f0ff8ed23964d20"
                },
                {
                  "introduced": "1929eeadf9b2bac12c5434fb56884ef27370580e"
                },
                {
                  "fixed": "49decca35e59d2cb774e5abd76412cee721308a5"
                }
              ],
              "database_specific": {
                "extracted_events": [
                  {
                    "cpe": "cpe:2.3:a:broadcom:rabbitmq_server:*:*:*:*:*:*:*:*",
                    "range": [
                      {
                        "introduced": "4.2.0"
                      },
                      {
                        "fixed": "4.2.6"
                      }
                    ],
                    "source": "CPE_RANGE"
                  },
                  {
                    "cpe": "cpe:2.3:a:broadcom:rabbitmq_server:*:*:*:*:*:*:*:*",
                    "range": [
                      {
                        "introduced": "4.3.0"
                      },
                      {
                        "fixed": "4.3.1"
                      }
                    ],
                    "source": "CPE_RANGE"
                  },
                  {
                    "range": [
                      {
                        "fixed": "8a56c37f099a7bf609a555de3f0ff8ed23964d20"
                      }
                    ],
                    "source": "REFERENCES_TAG",
                    "original_tag": "v4.2.6"
                  },
                  {
                    "range": [
                      {
                        "fixed": "49decca35e59d2cb774e5abd76412cee721308a5"
                      }
                    ],
                    "source": "REFERENCES_TAG",
                    "original_tag": "v4.3.1"
                  }
                ]
              }
            }
          ],
          "versions": [
            "v4.3.0",
            "v4.2.5",
            "v4.2.4",
            "v4.2.3",
            "v4.2.2",
            "v4.2.1",
            "v4.2.0"
          ],
          "database_specific": {
            "source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-67224.json"
          }
        }
      ],
      "modified": "2026-10-28T02:30:35.410028923Z",
      "provider": "osv",
      "references": [
        "https://github.com/rabbitmq/rabbitmq-server/releases/tag/v4.2.6",
        "https://github.com/rabbitmq/rabbitmq-server/releases/tag/v4.3.1",
        "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/67xxx/CVE-2026-67224.json",
        "https://github.com/rabbitmq/rabbitmq-server/security/advisories/GHSA-h7cq-qrr8-7vgc",
        "https://nvd.nist.gov/vuln/detail/CVE-2026-67224"
      ],
      "provider_metadata": {
        "cwe_ids": [
          "CWE-22"
        ],
        "cna_assigner": "GitHub_M",
        "unresolved_ranges": [
          {
            "extracted_events": [
              {
                "range": [
                  {
                    "introduced": "3.13.0"
                  },
                  {
                    "fixed": "3.13.15"
                  },
                  {
                    "introduced": "4.0.0"
                  },
                  {
                    "fixed": "4.0.20"
                  },
                  {
                    "introduced": "4.1.0"
                  },
                  {
                    "fixed": "4.1.11"
                  }
                ],
                "source": "AFFECTED_FIELD",
                "strategy": "StringRangeExpression"
              }
            ]
          }
        ],
        "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/67xxx/CVE-2026-67224.json"
      }
    },
    "related_cves": [
      {
        "value": "CVE-2026-67224",
        "evidence": "/id"
      }
    ],
    "security_relevant": true,
    "severity_evidence": "/severity/0/score"
  },
  "source_id": "core-osv",
  "document_id": 502944,
  "published_at": "2026-09-23T20:05:04.923+00:00"
}