CVE-2026-46495: CWE-502: Deserialization of Untrusted Data in OpenIdentityPlatform OpenDJ
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.
AI Analysis
Technical Summary
OpenDJ versions prior to 5.1.1 contain a deserialization of untrusted data vulnerability (CWE-502) in the JMX RMI connector. The connector processes attacker-controlled credential objects before authentication without a restrictive credentials filter pattern, and the RmiAuthenticator accepts an unconstrained Object array instead of a restricted String array. When the JMX Connection Handler is enabled and reachable, an unauthenticated remote attacker can submit crafted serialized Java objects to execute arbitrary code in the OpenDJ server process. Exploitation depends on the runtime classpath and Java version. The vulnerability was demonstrated on OpenDJ 4.4.15 with JDK 11 and Jackson 2.12.6.1. The vulnerability is resolved in OpenDJ 5.1.1.
Potential Impact
Successful exploitation allows unauthenticated remote attackers to execute arbitrary code on the OpenDJ server process, potentially leading to full system compromise. The attack requires the JMX Connection Handler to be enabled and reachable, which is disabled by default. The severity is critical with a CVSS 4.0 score of 9.2, indicating high impact on confidentiality, integrity, and availability.
Mitigation Recommendations
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.
CVE-2026-46495: CWE-502: Deserialization of Untrusted Data in OpenIdentityPlatform OpenDJ
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.
CVSS v4.0
Score 9.2critical
Affected software
OpenIdentityPlatform
OpenDJ
org.openidentityplatform.opendj
opendj-server-legacy
pkg:github/openidentityplatform/OpenDJRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
OpenDJ versions prior to 5.1.1 contain a deserialization of untrusted data vulnerability (CWE-502) in the JMX RMI connector. The connector processes attacker-controlled credential objects before authentication without a restrictive credentials filter pattern, and the RmiAuthenticator accepts an unconstrained Object array instead of a restricted String array. When the JMX Connection Handler is enabled and reachable, an unauthenticated remote attacker can submit crafted serialized Java objects to execute arbitrary code in the OpenDJ server process. Exploitation depends on the runtime classpath and Java version. The vulnerability was demonstrated on OpenDJ 4.4.15 with JDK 11 and Jackson 2.12.6.1. The vulnerability is resolved in OpenDJ 5.1.1.
Potential Impact
Successful exploitation allows unauthenticated remote attackers to execute arbitrary code on the OpenDJ server process, potentially leading to full system compromise. The attack requires the JMX Connection Handler to be enabled and reachable, which is disabled by default. The severity is critical with a CVSS 4.0 score of 9.2, indicating high impact on confidentiality, integrity, and availability.
Mitigation Recommendations
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.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-05-14T18:06:06.811Z
- Cvss Version
- 4.0
- State
- PUBLISHED
Threat ID: 6aa956ec55bf5e2cf5f0946f
Added to database: 09/15/2026, 14:32:12 UTC
Last enriched: 09/15/2026, 14:46:46 UTC
Last updated: 09/15/2026, 15:19:21 UTC
Views: 5
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.