{"answers":{"affected":"2 open source packages ship an affected version, including com.rabbitmq:amqp-client.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-63336 exists.","fix":"Upgrade com.rabbitmq:amqp-client to 5.33.0 or later.","what":"CVE-2026-63336 is a medium-severity vulnerability in rabbitmq-java-client, published on 18 Aug 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-63336 and fix it if it is affected.\n\nWhat it is: CVE-2026-63336 is a medium-severity vulnerability in rabbitmq-java-client, published on 18 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-63336 exists.\n\nAffected packages and fixed versions:\n- com.rabbitmq:amqp-client (Maven): affected all versions; fixed in 5.33.0\n- com.rabbitmq:amqp-client (Maven): affected all versions; fixed in 5.33.0\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-63336/ (Markdown: https://insights.sbomify.com/CVE-2026-63336/index.md)","id":"CVE-2026-63336","markdown":"https://insights.sbomify.com/CVE-2026-63336/index.md","name":"CVE-2026-63336","record":{"aliases":["CLEANSTART-2026-WB40347","CLSA-2026-1791800237","DEBIAN-CVE-2026-63336","ECHO-e155-bf0d-659d","GHSA-5m9f-rphj-c435","MINI-26m6-pjvc-m3xq","MINI-2fvw-98hc-qvfv","MINI-2rc4-rcp9-269h","MINI-2w6m-9j7r-fff7","MINI-53f6-6p83-j7vp","MINI-74xx-rr8r-7w2h","MINI-7hp5-x33m-rmvv","MINI-9458-94wq-3hpg","MINI-frwm-7hh8-vxcm","MINI-mcpx-7865-q2g2","MINI-p6xx-6qq6-8p58","MINI-prwp-pv75-h3ww","MINI-vcx5-5x67-f73c","MINI-vrqc-6gv7-g43c","MINI-wwc6-c3fh-cqrf","UBUNTU-CVE-2026-63336"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"RabbitMQ Java client","requires_auth":"low_privilege","summary":"A network attacker can perform man-in-the-middle attacks on RabbitMQ connections because the Java client library defaults to accepting any TLS certificate without hostname verification.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":5.1,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:N/VI:N/VA:N/SC:H/SI:L/SA:N","version":"4.0"},"cwes":[{"id":"CWE-295","name":"Improper Certificate Validation"}],"description":"The RabbitMQ Java client library allows Java and JVM-based applications to connect to and interact with RabbitMQ nodes. Prior to 5.33.0, com.rabbitmq.client.ConnectionFactory.useSslProtocol() and ConnectionFactory.useSslProtocol(String) configure com.rabbitmq.client.TrustEverythingTrustManager and leave hostname verification disabled, causing arbitrary server certificates, including self-signed certificates, to be accepted. A network attacker able to intercept a TLS connection can impersonate the RabbitMQ broker, read protected AMQP traffic, and modify traffic without certificate or hostname validation. The fix changes the production TLS helpers to use the JVM default trust store and enables hostname verification, while retaining an explicitly named development-only no-verification helper. This issue is fixed in version 5.33.0.","ecosystems":["Maven"],"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 Java client: TrustEverythingTrustManager used by default in useSslProtocol() enables MITM","id":"CVE-2026-63336","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"security_feature_bypass","year":"2026"},"n_packages":2,"n_references":6,"next":{"headline":"RabbitMQ Java client: Unvalidated Class.forName in JSON-RPC ProcedureDescription enables arbitrary class loading","id":"CVE-2026-63337"},"packages":[{"ecosystem":"Maven","fixed":["5.33.0"],"introduced":["0"],"last_affected":[],"package":"com.rabbitmq:amqp-client","purl":null,"source":"GHSA-5m9f-rphj-c435"},{"ecosystem":"Maven","fixed":["5.33.0"],"introduced":["0"],"last_affected":[],"package":"com.rabbitmq:amqp-client","purl":"pkg:maven/com.rabbitmq/amqp-client","source":"GHSA-5m9f-rphj-c435"}],"prev":{"headline":"RabbitMQ Java client malformed body frame triggers raw command assembler exception","id":"CVE-2026-63335"},"products":["rabbitmq-java-client"],"published":"2026-08-18","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"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-08-18","vendors":["rabbitmq"]},"summary":"A network attacker can perform man-in-the-middle attacks on RabbitMQ connections because the Java client library defaults to accepting any TLS certificate without hostname verification.","url":"https://insights.sbomify.com/CVE-2026-63336/"}