CVE-2026-46495

CRITICALPre-NVD 9.29.2
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This critical-severity CVE scores 9.2 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 1.1% (66th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Trending — 3 sources updated this week

Also known asEUVD-2026-78579 (ENISA EUVD) · GHSA-43x2-g84q-fmqx (GitHub Security Advisories)Source: ENISA EUVD

9.2EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1.1%CVSS: 9.2Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

OpenDJ is an LDAPv3 compliant directory service. Prior to 5.1.1, the JMX RMI connector in opendj-server-legacy/src/main/java/org/opends/server/protocols/jmx/RmiConnector.java processes attacker-controlled credential objects before authentication without a restrictive jmx.remote.rmi.server.credentials.filter.pattern, and RmiAuthenticator.authenticate in opendj-server-legacy/src/main/java/org/opends/server/protocols/jmx/RmiAuthenticator.java accepts an unconstrained Object array rather than a two-element String[]. When the JMX Connection Handler is enabled and its TCP listener is reachable, an unauthenticated remote attacker can submit a crafted serialized Java object and achieve code execution in the OpenDJ server process. The handler is disabled by default, and successful exploitation depends on the runtime classpath and Java version; remote code execution was demonstrated against OpenDJ 4.4.15 on JDK 11 with Jackson 2.12.6.1. This issue is fixed in 5.1.1.

CVSS v3
9.2
EG Score
9.2CRITICALmedium confidence
EG Risk
42
EG Risk 42/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity92% × 45%
Impact severity (EG Severity): CVSS 9.2 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation1.1% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
1.1%
EPSS %ILE
66th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.2): severity, escalated by confirmed exploitation. This CVE's 9.2 is its impact severity (EG Severity), not escalated.

EG Severity
9.2 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
1.1% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

June 22, 2026

Last Modified

September 25, 2026

Advisory Details (5)

Auto-updated Sep 15, 2026
Patch available. Sources: github_release, github, github_commit, github_pr.
GitHub advisoryMentions a patch (unverified)

OpenDJ Unauthenticated RCE via Java Deserialization in JMX RMI · Advisory · OpenIdentityPlatform/OpenDJ · GitHub

Affected: version 5.1.1.

https://github.com/OpenIdentityPlatform/OpenDJ/security/advisories/GHSA-43x2-g84q-fmqx
GitHub release Patch Available

5.1.1

Patch available: OpenIdentityPlatform/OpenDJ 5.1.1

https://github.com/OpenIdentityPlatform/OpenDJ/releases/tag/5.1.1
GitHub pull request

Fix JMX RMI connector startup failure introduced by CVE-2026-46495 hardening

Fix merged in OpenIdentityPlatform/OpenDJ PR #651 on 2026-06-11 — awaiting tagged release

https://github.com/OpenIdentityPlatform/OpenDJ/pull/651
GitHub commit

commit d4a95c2e37c3 (OpenIdentityPlatform/OpenDJ)

Fix landed in OpenIdentityPlatform/OpenDJ commit d4a95c2e37c3 — awaiting tagged release

https://github.com/OpenIdentityPlatform/OpenDJ/commit/d4a95c2e37c375756f9829c7ec43a4785b99e2e2
GitHub commit

commit 7e3a75903159 (OpenIdentityPlatform/OpenDJ)

Fix landed in OpenIdentityPlatform/OpenDJ commit 7e3a75903159 — awaiting tagged release

https://github.com/OpenIdentityPlatform/OpenDJ/commit/7e3a75903159153c877daeb2952a552701e38044

Vendor Advisories for CVE-2026-46495(1)

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

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
mavenorg.openidentityplatform.opendj:opendj-server-legacy @ 5.1.1 (fixes <= 5.1.0)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
Maven(1)
PackageVulnerable rangeFix by version rangeDependents
org.openidentityplatform.opendj:opendj-server-legacy4.10.0 ... 5.1.0 (41 versions)
  • every version up to 5.1.1: fixed in 5.1.1
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 15× in last 7d / 56× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

  1. 2026-11-01 16:34 UTCEPSS rescoreEPSS 1.1% · 66th percentile
  2. 2026-11-01 15:44 UTCGHSA enrichmentGHSA-43x2-g84q-fmqx · GitHub severity CRITICAL
  3. 2026-11-01 07:48 UTCGHSA enrichmentGHSA-43x2-g84q-fmqx · GitHub severity CRITICAL
  4. 2026-11-01 07:48 UTCEG score recompute
  5. 2026-10-31 16:32 UTCEPSS rescoreEPSS 1.1% · 66th percentile
  6. 2026-10-31 13:56 UTCEG score recompute
  7. 2026-10-30 16:34 UTCEPSS rescoreEPSS 1.1% · 66th percentile
  8. 2026-10-30 12:08 UTCEG score recompute
  9. 2026-10-29 16:33 UTCEPSS rescoreEPSS 1.1% · 66th percentile
  10. 2026-10-29 10:19 UTCEG score recompute
  11. 2026-10-28 16:32 UTCEPSS rescoreEPSS 1.1% · 66th percentile
  12. 2026-10-28 08:32 UTCEG score recompute
  13. 2026-10-27 16:32 UTCEPSS rescoreEPSS 1.1% · 66th percentile
  14. 2026-10-27 06:23 UTCEG score recompute
  15. 2026-10-26 16:31 UTCEPSS rescoreEPSS 1.1% · 66th percentile
  16. 2026-10-26 00:36 UTCEG score recompute
  17. 2026-10-25 16:33 UTCEPSS rescoreEPSS 1.1% · 66th percentile
  18. 2026-10-25 14:25 UTCEG score recompute
  19. 2026-10-24 22:44 UTCEG score recompute
  20. 2026-10-24 16:33 UTCEPSS rescoreEPSS 1.1% · 66th percentile
  21. 2026-10-23 20:57 UTCEG score recompute
  22. 2026-10-23 16:31 UTCEPSS rescoreEPSS 1.1% · 66th percentile
  23. 2026-10-22 19:09 UTCEG score recompute
  24. 2026-10-22 16:34 UTCEPSS rescoreEPSS 1.1% · 66th percentile
  25. 2026-10-21 17:19 UTCEG score recompute
Show 52 more
  1. 2026-10-21 16:33 UTCEPSS rescoreEPSS 1.1% · 66th percentile
  2. 2026-10-20 16:33 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  3. 2026-10-20 15:31 UTCEG score recompute
  4. 2026-10-19 16:32 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  5. 2026-10-19 13:42 UTCEG score recompute
  6. 2026-10-18 16:32 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  7. 2026-10-18 03:37 UTCEG score recompute
  8. 2026-10-17 16:34 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  9. 2026-10-17 10:05 UTCEG score recompute
  10. 2026-10-16 16:42 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  11. 2026-10-16 08:16 UTCEG score recompute
  12. 2026-10-15 16:32 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  13. 2026-10-15 06:27 UTCEG score recompute
  14. 2026-10-14 16:33 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  15. 2026-10-14 02:07 UTCEG score recompute
  16. 2026-10-13 16:34 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  17. 2026-10-12 22:25 UTCEG score recompute
  18. 2026-10-12 16:34 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  19. 2026-10-12 16:02 UTCEG score recompute
  20. 2026-10-11 19:45 UTCEG score recompute
  21. 2026-10-11 17:00 UTCEG score recompute
  22. 2026-10-11 14:25 UTCEG score recompute
  23. 2026-10-11 13:48 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  24. 2026-10-10 20:00 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  25. 2026-10-09 20:07 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  26. 2026-10-08 17:12 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  27. 2026-10-07 23:48 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  28. 2026-10-06 15:18 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  29. 2026-10-05 17:43 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  30. 2026-10-04 23:22 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  31. 2026-10-03 14:25 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  32. 2026-10-01 19:50 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  33. 2026-09-30 15:03 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  34. 2026-09-28 13:51 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  35. 2026-09-27 13:48 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  36. 2026-09-26 15:59 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  37. 2026-09-26 00:27 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  38. 2026-09-25 14:42 UTCEG score recompute
  39. 2026-09-23 17:53 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  40. 2026-09-20 20:15 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  41. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  42. 2026-09-18 11:14 UTCEG score recompute
  43. 2026-09-17 19:31 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  44. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  45. 2026-09-15 15:35 UTCEG score recompute
  46. 2026-09-15 15:02 UTCEG score recompute
  47. 2026-09-15 14:18 UTCEG score recomputeFirst assessed: 9.2 CRITICAL
  48. 2026-09-15 14:18 UTCMITRE cvelistV5CVSS v3 → 9.2 · CVSS v4 → 9.2
  49. 2026-08-01 13:12 UTCEG score recompute
  50. 2026-07-26 15:58 UTCEG score recompute
  51. 2026-07-23 03:17 UTCEG score recompute
  52. 2026-06-22 21:39 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-46495?
CVE-2026-46495 is a critical-severity vulnerability; its CVE record was published on June 22, 2026. OpenDJ is an LDAPv3 compliant directory service. Prior to 5.1.1, the JMX RMI connector in opendj-server-legacy/src/main/java/org/opends/server/protocols/jmx/RmiConnector.java processes attacker-controlled credential objects before authentication without a restrictive…
When was the CVE record for CVE-2026-46495 published?
The CVE record for CVE-2026-46495 was published on June 22, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of September 25, 2026; the record at its source may have been updated since.
Is CVE-2026-46495 actively exploited?
CVE-2026-46495 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.1% probability of exploitation in the next 30 days (66th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-46495?
CVE-2026-46495 has a CVSS base score of 9.2 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-46495?
A fix for CVE-2026-46495 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-46495 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-46495

Explore →

Is Your Infrastructure Affected by CVE-2026-46495?

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