{"answers":{"affected":"2 open source packages ship an affected version, including org.jolokia:jolokia-service-jsr160.","exploited":"There is no known exploitation of CVE-2026-84218 in the wild and no public exploit code.","fix":"Upgrade org.jolokia:jolokia-service-jsr160 to 2.6.2 or later.","what":"CVE-2026-84218 is a high-severity server-side request forgery vulnerability in Red Hat AMQ Broker 7, published on 1 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-84218 and fix it if it is affected.\n\nWhat it is: CVE-2026-84218 is a high-severity server-side request forgery vulnerability in Red Hat AMQ Broker 7, published on 1 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-84218 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- org.jolokia:jolokia-service-jsr160 (Maven): affected all versions; fixed in 2.6.2\n- org.jolokia:jolokia-service-jsr160 (Maven): affected all versions; fixed in 2.6.2\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-84218/ (Markdown: https://insights.sbomify.com/CVE-2026-84218/index.md)","id":"CVE-2026-84218","markdown":"https://insights.sbomify.com/CVE-2026-84218/index.md","name":"CVE-2026-84218","record":{"aliases":["ECHO-17d4-6e0b-374f","GHSA-c9ff-59g8-m36q","MINI-28vp-pr5c-3gm7","MINI-fv52-2vpc-5rc8"],"analysis":{"component_type":"library","fix_type":"patch","impacts":["data_read","code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Java monitoring library","requires_auth":"none","summary":"Attackers can bypass JNDI denylists in Jolokia's JSR-160 proxy to trigger SSRF and potential remote code execution via crafted JMX URLs.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"redhat","cpe":[],"cvss":{"score":8.1,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-184","name":"Incomplete List of Disallowed Inputs"}],"description":"A flaw was found in Jolokia's JSR-160 proxy functionality where insufficient validation of client-controlled JMX service URLs allows a bypass of the denylist introduced to mitigate CVE-2018-1000130. The proxy accepts a `target.url` value from a Jolokia POST request and passes it to `JMXServiceURL` and `JMXConnectorFactory` for establishing the remote JMX connection. The existing denylist only rejects URLs matching `service:jmx:rmi:///jndi/ldap:.*`, which can be bypassed using alternative valid JMX service URL forms, including `ldaps://` schemes or LDAP URLs with a non-empty JMX host component. These URLs are accepted as valid `JMXServiceURL` objects and can cause the Jolokia agent JVM to perform a JNDI lookup against an attacker-controlled LDAP endpoint. This can result in server-side request forgery (SSRF), forwarding of supplied JMX credentials to the remote endpoint, and potentially remote code execution depending on the classes and configuration available in the target JVM.","ecosystems":["Maven"],"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":"Org.jolokia/jolokia-core: incomplete jndi denylist in jolokia jsr-160 proxy (bypass of cve-2018-1000130 fix)","id":"CVE-2026-84218","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"ssrf","year":"2026"},"n_packages":2,"n_references":5,"next":{"headline":"Kirki 6.2.1 - 6.2.5 - Unauthenticated Stored XSS via HTML Entity Decoding","id":"CVE-2026-84219"},"packages":[{"ecosystem":"Maven","fixed":["2.6.2"],"introduced":["0"],"last_affected":[],"package":"org.jolokia:jolokia-service-jsr160","purl":null,"source":"GHSA-c9ff-59g8-m36q"},{"ecosystem":"Maven","fixed":["2.6.2"],"introduced":["0"],"last_affected":[],"package":"org.jolokia:jolokia-service-jsr160","purl":"pkg:maven/org.jolokia/jolokia-service-jsr160","source":"GHSA-c9ff-59g8-m36q"}],"prev":{"headline":"WordPress Classified Listing plugin \u003c= 6.1.3 - Broken Access Control vulnerability","id":"CVE-2026-84217"},"products":["Red Hat AMQ Broker 7","Red Hat Fuse 7","Red Hat Satellite 6","Red Hat build of Apache Camel 4 for Quarkus 3","Red Hat build of Apache Camel for Spring Boot 4"],"published":"2026-09-01","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":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-09-02","vendors":["Red Hat"]},"summary":"Attackers can bypass JNDI denylists in Jolokia's JSR-160 proxy to trigger SSRF and potential remote code execution via crafted JMX URLs.","url":"https://insights.sbomify.com/CVE-2026-84218/"}