{"answers":{"affected":"1 open source package ship an affected version, including rabbitmq. It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-67409 exists.","fix":"Upgrade rabbitmq to a fixed version for your release line: 3.13.18, 4.0.23, 4.1.14 or 4.2.9.","what":"CVE-2026-67409 is a high-severity denial of service vulnerability in Broadcom Rabbitmq Server, published on 25 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-67409 and fix it if it is affected.\n\nWhat it is: CVE-2026-67409 is a high-severity denial of service vulnerability in Broadcom Rabbitmq Server, published on 25 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-67409 exists.\n\nAffected packages and fixed versions:\n- rabbitmq (Bitnami): affected from 3.13.0; fixed in 3.13.18, 4.0.23, 4.1.14, 4.2.9, 4.3.3\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-67409/ (Markdown: https://insights.sbomify.com/CVE-2026-67409/index.md)","id":"CVE-2026-67409","markdown":"https://insights.sbomify.com/CVE-2026-67409/index.md","name":"CVE-2026-67409","record":{"aliases":["AZL-109731","BIT-rabbitmq-2026-67409","DEBIAN-CVE-2026-67409","GHSA-qw3h-qqm9-jrw8","UBUNTU-CVE-2026-67409"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":true,"product_category":"RabbitMQ message broker","requires_auth":"none","summary":"Attackers can cause persistent authentication denial of service by triggering JWKS fetch errors that destroy cached signing keys in RabbitMQ.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"rabbitmq_server","vendor":"broadcom"}],"cvss":{"score":8.2,"severity":"high","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","version":"4.0"},"cwes":[{"id":"CWE-252","name":"Unchecked Return Value"}],"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.","ecosystems":["Bitnami"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"RabbitMQ: JWKS Fetch Ignores HTTP Response Status Code - Signing Key Destruction Causes Authentication DoS","id":"CVE-2026-67409","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Bitnami","product":"broadcom:rabbitmq_server","products":["broadcom:rabbitmq_server"],"type":"denial_of_service","year":"2026"},"n_packages":1,"n_references":3,"next":{"headline":"RabbitMQ: OAuth2 Client Secret Exposed via Unauthenticated JavaScript Endpoint","id":"CVE-2026-67410"},"packages":[{"ecosystem":"Bitnami","fixed":["3.13.18","4.0.23","4.1.14","4.2.9","4.3.3"],"introduced":["3.13.0","4.0.0","4.1.0","4.2.0","4.3.0"],"last_affected":[],"package":"rabbitmq","purl":"pkg:bitnami/rabbitmq","source":"BIT-rabbitmq-2026-67409"}],"prev":{"headline":"RabbitMQ: Stream Management Super-Stream Binding Keys Allocation Allows Low-Privilege Node Denial of Service","id":"CVE-2026-67408"},"products":["rabbitmq-server"],"published":"2026-09-25","related":[{"cvss_score":9.8,"headline":"Auth bypass in Pivotal RabbitMQ 3.x before 3.5.8 and 3.6.x before 3.6.6; RabbitMQ for PCF 1.5.x before 1.5.20, 1.6.x before 1.6.12 and 1.7.x before 1.7.7","id":"CVE-2016-9877","kev_date_added":null,"published":"2016-12-29"},{"cvss_score":9.2,"headline":"RabbitMQ: OAuth2 silent verify_none fallback for JWKS fetch","id":"CVE-2026-67404","kev_date_added":null,"published":"2026-09-23"},{"cvss_score":9.1,"headline":"RabbitMQ: Trust-store whitelist by Issuer+Serial only","id":"CVE-2026-67231","kev_date_added":null,"published":"2026-09-23"},{"cvss_score":8.7,"headline":"Information disclosure in rabbitmq-server","id":"CVE-2026-57219","kev_date_added":null,"published":"2026-07-10"},{"cvss_score":8.2,"headline":"RabbitMQ: Plaintext username:password stored in an insecure cookie after successful POST /login","id":"CVE-2026-67236","kev_date_added":null,"published":"2026-09-25"},{"cvss_score":8.2,"headline":"RabbitMQ: OAuth2 Client Secret Exposed via Unauthenticated JavaScript Endpoint","id":"CVE-2026-67410","kev_date_added":null,"published":"2026-09-25"}],"sources":[{"class":"attribution","licence":"Apache-2.0","name":"Bitnami","prefix":"BIT"},{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-09-25","vendors":["rabbitmq"]},"summary":"Attackers can cause persistent authentication denial of service by triggering JWKS fetch errors that destroy cached signing keys in RabbitMQ.","url":"https://insights.sbomify.com/CVE-2026-67409/"}