CVE-2026-46495: OpenIdentityPlatform OpenDJ · Deserialization of Untrusted Data
Affects OpenIdentityPlatform OpenDJSource CVE Database V5
Not known to be exploited · CVSS 9.2 Critical : upgrade to 5.1.1 as a priority.
Data as of 30 Oct 2026, 20:25 UTC
- EPSS
- 1.1% chance of exploitation in 30 days – higher than 66% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 5.1.1
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 15 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.
What to do
Upgrade OpenDJ and opendj-server-legacy and openidentityplatform/OpenDJ to 5.1.1.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| OpenIdentityPlatformOpenDJ | Affected
| Fixed in
|
| org.openidentityplatform.opendjopendj-server-legacy | Affected
| Fixed in
|
GitHubopenidentityplatform/OpenDJpkg:github/openidentityplatform/OpenDJOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade OpenDJ to version 5.1.1 or later, where this vulnerability is fixed. If upgrading is not immediately possible, ensure that the JMX Connection Handler is disabled (default setting) to prevent exposure. Review runtime environment and classpath to reduce attack surface. Patch status is confirmed fixed in 5.1.1.
Description
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.
References
- github.com/OpenIdentityPlatform/OpenDJ/security/advisories/GHSA-43x2-g84q-fmqx (opens in a new tab)
- github.com/OpenIdentityPlatform/OpenDJ/pull/651 (opens in a new tab)
- github.com/OpenIdentityPlatform/OpenDJ/commit/7e3a75903159153c877daeb2952a552701e38044 (opens in a new tab)
- github.com/OpenIdentityPlatform/OpenDJ/commit/d4a95c2e37c375756f9829c7ec43a4785b99e2e2 (opens in a new tab)
- github.com/OpenIdentityPlatform/OpenDJ/releases/tag/5.1.1 (opens in a new tab)