CVE-2026-84218

HIGHPre-NVD 8.18.1—
EchelonGraph scoreHIGH confidence

Score 8.1 from GitHub Security Advisory (severity: HIGH) published 2026-09-01. a secondary CVSS source baseline 8.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
8.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 8.1Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
8.1
EG Score
8.1(high)
EG Risk
37(Track)
EG Risk 37/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity81% × 45%
Exploitation1% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
58%
KEV
Not listed

Published

September 1, 2026

Last Modified

September 2, 2026

Advisory Details (3)

Auto-updated Sep 1, 2026
🔬 Proof of concept available. Patch available. Sources: redhat.
generic🟡 PoC Available

Incomplete JNDI Denylist in Jolokia JSR-160 Proxy (Bypass of CVE-2018-1000130 Fix) · Issue #1049 · jolokia/jolokia · GitHub

https://github.com/jolokia/jolokia/issues/1049
redhat

2526752 – (CVE-2026-84218) CVE-2026-84218 org.jolokia/jolokia-core: Incomplete JNDI Denylist in Jolokia JSR-160 Proxy (Bypass of CVE-2018-1000130 Fix)

https://bugzilla.redhat.com/show_bug.cgi?id=2526752
redhat Patch Available

CVE-2026-84218 - Red Hat Customer Portal

Affected: Red Hat Enterprise Linux 8 or OpenShift Container Platform 4, is affected by this vulnerability and a fix may be released to a

https://access.redhat.com/security/cve/CVE-2026-84218

Vendor Advisories for CVE-2026-84218(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 28× in last 7d / 85× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-09-19 06:20 UTCEG score recompute
  2. 2026-09-19 06:20 UTCGHSA enrichment
  3. 2026-09-18 19:28 UTCEPSS rescore
  4. 2026-09-18 19:15 UTCGHSA enrichment
  5. 2026-09-18 08:10 UTCGHSA enrichment
  6. 2026-09-17 21:05 UTCEG score recompute
  7. 2026-09-17 21:05 UTCGHSA enrichment
  8. 2026-09-17 19:32 UTCEPSS rescore
  9. 2026-09-17 09:58 UTCGHSA enrichment
  10. 2026-09-16 22:53 UTCEG score recompute
  11. 2026-09-16 22:53 UTCGHSA enrichment
  12. 2026-09-16 14:09 UTCEPSS rescore
  13. 2026-09-16 11:48 UTCEG score recompute
  14. 2026-09-16 11:48 UTCGHSA enrichment
  15. 2026-09-16 05:15 UTCEPSS rescore
  16. 2026-09-16 00:43 UTCGHSA enrichment
  17. 2026-09-15 13:36 UTCEG score recompute
  18. 2026-09-15 13:36 UTCGHSA enrichment
  19. 2026-09-15 03:12 UTCEPSS rescore
  20. 2026-09-15 03:12 UTCEPSS rescore
  21. 2026-09-15 02:31 UTCGHSA enrichment
  22. 2026-09-14 15:23 UTCGHSA enrichment
  23. 2026-09-14 04:16 UTCGHSA enrichment
  24. 2026-09-13 17:11 UTCEG score recompute
  25. 2026-09-13 17:11 UTCGHSA enrichment
Show 60 more
  1. 2026-09-13 06:06 UTCGHSA enrichment
  2. 2026-09-12 19:01 UTCEG score recompute
  3. 2026-09-12 19:01 UTCGHSA enrichment
  4. 2026-09-12 07:56 UTCGHSA enrichment
  5. 2026-09-11 20:51 UTCEG score recompute
  6. 2026-09-11 20:51 UTCGHSA enrichment
  7. 2026-09-11 14:53 UTCEPSS rescore
  8. 2026-09-11 14:53 UTCEPSS rescore
  9. 2026-09-11 09:46 UTCEG score recompute
  10. 2026-09-11 09:46 UTCGHSA enrichment
  11. 2026-09-10 22:41 UTCGHSA enrichment
  12. 2026-09-10 11:36 UTCEG score recompute
  13. 2026-09-10 11:36 UTCGHSA enrichment
  14. 2026-09-09 23:38 UTCGHSA enrichment
  15. 2026-09-09 10:32 UTCGHSA enrichment
  16. 2026-09-08 23:24 UTCEG score recompute
  17. 2026-09-08 23:24 UTCGHSA enrichment
  18. 2026-09-08 22:01 UTCEPSS rescore
  19. 2026-09-08 10:02 UTCGHSA enrichment
  20. 2026-09-07 22:50 UTCEG score recompute
  21. 2026-09-07 22:50 UTCGHSA enrichment
  22. 2026-09-07 11:45 UTCGHSA enrichment
  23. 2026-09-07 00:36 UTCEG score recompute
  24. 2026-09-07 00:36 UTCGHSA enrichment
  25. 2026-09-06 13:48 UTCEPSS rescore
  26. 2026-09-06 13:31 UTCGHSA enrichment
  27. 2026-09-06 02:26 UTCEG score recompute
  28. 2026-09-06 02:26 UTCGHSA enrichment
  29. 2026-09-05 15:31 UTCEPSS rescore
  30. 2026-09-05 15:21 UTCGHSA enrichment
  31. 2026-09-05 04:14 UTCGHSA enrichment
  32. 2026-09-04 17:09 UTCEG score recompute
  33. 2026-09-04 17:08 UTCGHSA enrichment
  34. 2026-09-04 06:02 UTCEG score recompute
  35. 2026-09-04 06:01 UTCGHSA enrichment
  36. 2026-09-04 05:07 UTCEPSS rescore
  37. 2026-09-03 18:54 UTCGHSA enrichment
  38. 2026-09-03 07:37 UTCGHSA enrichment
  39. 2026-09-02 20:32 UTCEG score recompute
  40. 2026-09-02 20:32 UTCGHSA enrichment
  41. 2026-09-02 14:12 UTCEPSS rescore
  42. 2026-09-02 09:27 UTCEG score recompute
  43. 2026-09-02 09:26 UTCGHSA enrichment
  44. 2026-09-02 08:34 UTCEG score recompute
  45. 2026-09-02 08:34 UTCGHSA enrichment
  46. 2026-09-02 08:14 UTCGHSA enrichment
  47. 2026-09-01 21:08 UTCEG score recompute
  48. 2026-09-01 21:08 UTCGHSA enrichment
  49. 2026-09-01 17:04 UTCEG score recompute
  50. 2026-09-01 17:04 UTCGHSA enrichment
  51. 2026-09-01 16:27 UTCEG score recompute
  52. 2026-09-01 16:26 UTCGHSA enrichment
  53. 2026-09-01 16:10 UTCEG score recompute
  54. 2026-09-01 16:10 UTCGHSA enrichment
  55. 2026-09-01 15:40 UTCEG score recompute
  56. 2026-09-01 15:40 UTCGHSA enrichment
  57. 2026-09-01 15:04 UTCEG score recompute
  58. 2026-09-01 14:34 UTCEG score recompute
  59. 2026-09-01 13:30 UTCEG score recompute
  60. 2026-09-01 13:29 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-84218?
CVE-2026-84218 is a high vulnerability published on September 1, 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…
When was CVE-2026-84218 disclosed?
CVE-2026-84218 was first published in the National Vulnerability Database on September 1, 2026, with the most recent update on September 2, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-84218 actively exploited?
CVE-2026-84218 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 42.5% of all scored CVEs.
What is the CVSS score of CVE-2026-84218?
CVE-2026-84218 has a CVSS v3 base score of 8.1 (NVD).
How do I remediate CVE-2026-84218?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-84218, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-84218

Explore →

Is Your Infrastructure Affected by CVE-2026-84218?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs