CVE-2026-46495

published 15 Sep 2026 · updated 15 Sep 2026

OpenDJ Pre-Auth RCE via Java Deserialization in JMX RMI

9.2CriticalCVSS 9.2EPSS 1%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 1%. No fixed version is recorded.

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.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
OpenIdentityPlatform<5.1.1
org.openidentityplatform.opendj<5.1.1

Timeline

Every event on this vulnerability

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-46495 severity on Zeptric[![CVE-2026-46495](https://zeptric.io/badge/cve/CVE-2026-46495.svg)](https://zeptric.io/cve/CVE-2026-46495)