{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-57215 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2026-57215 is a high-severity missing authorization vulnerability in Broadcom Rabbitmq Server, published on 10 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-57215 and fix it if it is affected.\n\nWhat it is: CVE-2026-57215 is a high-severity missing authorization vulnerability in Broadcom Rabbitmq Server, published on 10 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-57215 in the wild and no public exploit code.\n\nAffected product: Broadcom Rabbitmq Server. No package-level version data is available, so check the vendor advisory linked from the reference page.\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-57215/ (Markdown: https://insights.sbomify.com/CVE-2026-57215/index.md)","id":"CVE-2026-57215","markdown":"https://insights.sbomify.com/CVE-2026-57215/index.md","name":"CVE-2026-57215","record":{"aliases":["AZL-92364","DEBIAN-CVE-2026-57215","GHSA-5cq3-v9jx-p3x3","UBUNTU-CVE-2026-57215","openSUSE-SU-2026:22163-1"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"RabbitMQ message broker","requires_auth":"low_privilege","summary":"Attackers can inject unauthorized replies into direct-reply-to channels due to missing deletion checks, potentially intercepting sensitive data.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"rabbitmq_server","vendor":"broadcom"}],"cvss":{"score":7,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:H/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-863","name":"Incorrect Authorization"}],"description":"RabbitMQ is a messaging and streaming broker. Prior to 3.13.15, 4.0.20, 4.1.11, and 4.2.6, RabbitMQ allows foreign bindings to amq.rabbitmq.reply-to destinations because volatile direct-reply-to queues can be accepted at bind and route time but are missing from Khepri-backed deletion checks, leaving persistent route entries after unbind. This issue is fixed in versions 3.13.15, 4.0.20, 4.1.11, and 4.2.6.","ecosystems":["openSUSE:Leap 16.0"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"RabbitMQ: Direct-reply-to binding persistence can lead to unauthorized reply-channel injection and persistent phantom","id":"CVE-2026-57215","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"broadcom:rabbitmq_server","products":["broadcom:rabbitmq_server"],"type":"missing_authorization","year":"2026"},"n_packages":1,"n_references":6,"next":{"headline":"Auth bypass in rabbitmq-server","id":"CVE-2026-57216"},"packages":[{"ecosystem":"openSUSE:Leap 16.0","fixed":["4.1.5-160000.3.1"],"introduced":["0"],"last_affected":[],"package":"rabbitmq-server","purl":"pkg:rpm/opensuse/rabbitmq-server\u0026distro=openSUSE%20Leap%2016.0","source":"openSUSE-SU-2026:22163-1"}],"prev":{"headline":"RabbitMQ: Stored XSS in RabbitMQ management UI","id":"CVE-2026-57214"},"products":["rabbitmq-server"],"published":"2026-07-10","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: JWKS Fetch Ignores HTTP Response Status Code - Signing Key Destruction Causes Authentication DoS","id":"CVE-2026-67409","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":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"SUSE","prefix":"openSUSE"},{"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":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-07-13","vendors":["rabbitmq"]},"summary":"Attackers can inject unauthorized replies into direct-reply-to channels due to missing deletion checks, potentially intercepting sensitive data.","url":"https://insights.sbomify.com/CVE-2026-57215/"}