jolokia-service-jsr160 Incomplete target JMX Service URL deny list handling for user-controlled input
CVE-2026-84218GHSA-c9ff-59g8-m36q
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (org.jolokia:jolokia-service-jsr160 2.6.2), redeploy, then verify what is actually installed.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
Maven org.jolokia:jolokia-service-jsr160
- Affected
- < 2.6.2
- Fixed in
- 2.6.2
Sources
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record GHSA-c9ff-59g8-m36q lists affected ranges: Maven org.jolokia:jolokia-service-jsr160 >=0 <2.6.2 (fixed)
VerifiedObserved Structured OSV record; GitHub-reviewed advisory.
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-c9ff-59g8-m36q lists affected ranges: Maven org.jolokia:jolokia-service-jsr160 >=0 <2.6.2
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS
- 7.5 · CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
- EPSS
- CVE-2026-84218: 0.95% estimated exploitation activity in the next 30 days; percentile 61.26 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description
As published by the source; long descriptions are shortened.
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.
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 2 · amended ·
Amended from ghsa record GHSA-c9ff-59g8-m36q
- Revision 1 · created ·
Published from osv record GHSA-c9ff-59g8-m36q
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: CVE-2026-84218 Advisory: jolokia-service-jsr160 Incomplete target JMX Service URL deny list handling for user-controlled input IDs: CVE-2026-84218, GHSA-c9ff-59g8-m36q Record: https://patchnext.com/advisories/cve-2026-84218 (revision 2, source checked 26 Oct 2026, 16:58 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: High (CVSS 7.5) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor fix available; fixed versions by package: org.jolokia:jolokia-service-jsr160 2.6.2. A vendor fix does not mean a deployment is fixed. ## Affected components - Maven org.jolokia:jolokia-service-jsr160: affected < 2.6.2; fixed in 2.6.2 ## Suggested inspection (read-only) - Maven org.jolokia:jolokia-service-jsr160: check the installed version with your package manager. ## Supported action Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on org.jolokia:jolokia-service-jsr160. - Repeat the inspection and confirm that only fixed versions remain installed. ## Rollback considerations - Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward. ## Unresolved questions - Which deployments run an affected version? - Exploitation status can change. Check again before lowering the priority. - Mark the work resolved only after the fixed version is verified in production. ## Sources - Verified: https://osv.dev/vulnerability/GHSA-c9ff-59g8-m36q (OSV record GHSA-c9ff-59g8-m36q lists affected ranges: Maven org.jolokia:jolokia-service-jsr160 >=0 <2.6.2 (fixed)) - Verified: https://github.com/advisories/GHSA-c9ff-59g8-m36q (GitHub-reviewed advisory GHSA-c9ff-59g8-m36q lists affected ranges: Maven org.jolokia:jolokia-service-jsr160 >=0 <2.6.2) Commands are suggestions: review each one before running it.
Loading voting…