CVE-2026-84218
HIGHDescription
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.
How to fix
No published remediation has been found for this vulnerability's affected products yet.
Mitigation guidance may be in the linked vendor advisories in the References section below.
TridentStack Control tracks known vulnerabilities across your Windows, macOS, and Linux fleet and shows the fix as soon as one is published. See how it works
CVSS v3 Vector
Exploitability
Impact
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
Exploit Intelligence
Moderate risk: more likely to be exploited than 57% of all known CVEs.
References
Related Vulnerabilities
Other CWE-184 vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2024-5217 | Critical | 9.8 | 100% | KEV | - |
| CVE-2022-43396 | High | 8.8 | 55% | - | Fix |
| CVE-2017-7525 | Critical | 9.8 | 38% | - | Fix |
| CVE-2024-5178 | Medium | 4.9 | 34% | - | - |
| CVE-2018-7489 | Critical | 9.8 | 20% | - | Fix |
| CVE-2018-6383 | High | 8.8 | 13% | - | - |
Common questions
How do I fix CVE-2026-84218?
No published fix for CVE-2026-84218 has been found yet. Check the linked vendor advisories for guidance as it becomes available.
Is CVE-2026-84218 being actively exploited?
Not that we know of. CVE-2026-84218 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.88% is the estimated probability that it will be exploited in the next 30 days. That is higher than 57% of all scored CVEs.
How severe is CVE-2026-84218?
CVE-2026-84218 has a CVSS v3 base score of 8.1, rated high. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
Embed a live status badge for CVE-2026-84218
Markdown
[](https://tridentstack.com/cve/CVE-2026-84218)HTML
<a href="https://tridentstack.com/cve/CVE-2026-84218"><img src="https://tridentstack.com/cve/badge/CVE-2026-84218.svg" alt="CVE-2026-84218"></a>Find and fix vulnerabilities across your fleet
TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-09-02.