{
  "id": "CVE-2026-67409",
  "url": "https://poc.griffinguard.io/cve/CVE-2026-67409",
  "published_at": "2026-09-25T16:18:25.611Z",
  "title": "RabbitMQ: JWKS Fetch Ignores HTTP Response Status Code - Signing Key Destruction Causes Authentication DoS",
  "vendor": "rabbitmq",
  "product": "rabbitmq-server",
  "cvss": {
    "score": 8.2,
    "source": "cna",
    "vector": "CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N"
  },
  "kev": {
    "in_kev": false,
    "added_at": null,
    "days_after_publication": null
  },
  "first_poc": null,
  "poc_repo_count": 0,
  "exploit_count": 0,
  "suspicious_repo_count": 0,
  "edge_device": null,
  "description": "RabbitMQ is a messaging and streaming broker. From 3.13.0 until 4.3.3, 4.2.9, 4.1.14, 4.0.23, and 3.13.18, JWKS Fetch Ignores HTTP Response Status Code - Signing Key Destruction Causes Authentication DoS (CWE-252). the JWKS key fetching mechanism in uaajwt.erl does not validate the HTTP response status code when downloading signing keys from the OAuth2 provider's JWKS endpoint. Non-200 responses (including 4xx and 5xx errors) are processed identically to successful responses. When the JWKS endpoint returns an error response with a valid-JSON body that lacks a keys field, all previously cached signing keys are destroyed, causing a persistent authentication denial of Files: deps/rabbitmqauthbackendoauth2/src/uaajwt.erl, lines 50-63 deps/rabbitmqauthbackendoauth2/src/uaajwks.erl, lines 5-7 deps/rabbitmqauthbackendoauth2/src/rabbitoauth2provider.erl, lines 98-107 Bug 1: HTTP status code ignored (uaajwt.erl:50-63): The Erlang httpc module returns {ok, {{HttpVersion, StatusCode, ReasonPhrase}, Headers, Body}}. The pattern {ok, {, , JwksBody}} matches ANY successful HTTP transaction Persistent authentication DoS: Once keys are destroyed, ALL OAuth2/JWT authentication fails for all users until a new successful JWKS refresh occurs Amplification: A single attacker can deny access to all legitimate OAuth2 users across the entire RabbitMQ. This issue is fixed in versions 4.3.3, 4.2.9, 4.1.14, 4.0.23, and 3.13.18.",
  "cwe": "CWE-252",
  "cpes": [
    "cpe:2.3:a:broadcom:rabbitmq_server:*:*:*:*:*:*:*:*"
  ],
  "cvss_by_source": {
    "cna": 8.2,
    "nvd": 6.5
  },
  "repos": [],
  "remediation": {
    "affected": [
      {
        "vendor": "rabbitmq",
        "product": "rabbitmq-server",
        "ranges": [
          "\u003e= 4.3.0, \u003c 4.3.3",
          "\u003e= 4.2.0, \u003c 4.2.9",
          "\u003e= 4.1.0, \u003c 4.1.14",
          "\u003e= 4.0.0, \u003c 4.0.23",
          "\u003e= 3.13.0, \u003c 3.13.18"
        ],
        "fixed_in": [
          "4.3.3",
          "4.2.9",
          "4.1.14",
          "4.0.23",
          "3.13.18"
        ]
      }
    ],
    "upgrade": [
      "Upgrade rabbitmq-server to 4.3.3 or 4.2.9 or 4.1.14 or 4.0.23 or 3.13.18 or later."
    ],
    "references": [
      {
        "kind": "Vendor advisory",
        "url": "https://github.com/rabbitmq/rabbitmq-server/security/advisories/GHSA-qw3h-qqm9-jrw8"
      },
      {
        "kind": "Release notes",
        "url": "https://github.com/rabbitmq/rabbitmq-server/releases/tag/v4.2.9"
      },
      {
        "kind": "Release notes",
        "url": "https://github.com/rabbitmq/rabbitmq-server/releases/tag/v4.3.3"
      }
    ]
  },
  "exploit_refs": [],
  "hunt_profile": [],
  "rules": []
}
