CVE-2026-84218
Last modified
CVE-2026-84218 is a high-severity vulnerability rated 8.1/10 on the CVSS scale. 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.
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.
Metrics
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
Weakness Enumeration
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Red Hat | Red Hat build of Apache Camel 4 for Quarkus 3 | All versions |
| Red Hat | Red Hat build of Apache Camel for Spring Boot 4 | All versions |
| Red Hat | Red Hat Fuse 7 | All versions |
| Red Hat | Red Hat Satellite 6 | All versions |
References
Timeline
- Published
- Last Modified
- Status
- Received
Frequently Asked Questions
What is CVE-2026-84218?
How severe is CVE-2026-84218?
How do I fix CVE-2026-84218?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-84195Kyverno before 1.16.4 automatically attaches the admission c…7.7
- CVE-2026-84196Kyverno before 1.18.0 contains a server-side request forgery…7.7
- CVE-2026-84199Kyverno before 1.16.2 contains a server-side request forgery…7.7
- CVE-2026-8420The BLOGCHAT Chat System plugin for WordPress is vulnerable …6.1
- CVE-2026-84200Kyverno versions v1.9.0 through v1.12.7 contain a policy exc…9
- CVE-2026-8421Concrete CMS 9.5.0 and below contains a CSRF vulnerability i…8.8
- CVE-2026-8422The Remove meta boxes per user role plugin for WordPress is …4.3
- CVE-2026-8423The JaviBola Custom Theme Test plugin for WordPress is vulne…4.3
- CVE-2026-84235A denial-of-service security issue exists in the affected pr…8.7
- CVE-2026-8424The Remove Yellow BGBOX plugin for WordPress is vulnerable t…4.3
- CVE-2026-8425The Notify Odoo plugin for WordPress is vulnerable to Cross-…4.3
- CVE-2026-8426Concrete CMS 9.5.0 and below does not validate a CSRF token …8.8
Are you affected by CVE-2026-84218?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST