CVE-2026-84218 PUBLISHED

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

Assigner: redhat
Reserved: 01.09.2026 Published: 01.09.2026 Updated: 01.09.2026

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.

Metrics

CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
CVSS Score: 8.1

Product Status

Vendor Red Hat
Product Red Hat build of Apache Camel 4 for Quarkus 3
Versions Default: unknown
Vendor Red Hat
Product Red Hat build of Apache Camel for Spring Boot 4
Versions Default: unknown
Vendor Red Hat
Product Red Hat Fuse 7
Versions Default: unknown
Vendor Red Hat
Product Red Hat Satellite 6
Versions Default: unknown

Credits

  • This issue was discovered by Sandipan Roy (Red Hat).

References

Problem Types

  • Incomplete List of Disallowed Inputs CWE