Unrated

Pre-authentication RCE in OpenDJ Community Edition JMX RMI Connector

IdentifiersCVE-2026-46495CWE-502

CVE-2026-46495 is a pre-authentication remote code execution vulnerability in OpenDJ Community Edition affecting the JMX RMI connector. The flaw is caused by unsafe Java deserialization of untrusted data received by the JMX RMI listener before authentication is completed. An unauthenticated attacker with network reachability to the exposed JMX service can supply a crafted serialized object stream and trigger deserialization in the target JVM. In environments where suitable gadget chains are present on the runtime classpath, successful exploitation can result in arbitrary code execution. Unauthenticated remote code execution was demonstrated against OpenDJ 4.4.15 running on JDK 11 with Jackson 2.12.6.1 present in the classpath.

For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

Start free trial

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation can allow an unauthenticated remote attacker to execute arbitrary code in the context of the OpenDJ process before authentication. The practical impact depends on the available deserialization gadget chains, the runtime classpath, and Java runtime characteristics, but may include full compromise of the affected service, unauthorized access to directory data, modification of application state, deployment of persistence mechanisms, and use of the host as a pivot point for further intrusion.

Mitigation

If you can’t patch tonight, do this now.

If immediate patching is not possible, disable the JMX Connection Handler where operationally feasible, because exploitation requires that this component be enabled. Additionally, restrict network access to the JMX RMI listener to trusted administrative hosts only through firewall rules, access control lists, segmentation, or binding the service to non-public interfaces. Reducing the exposed classpath and limiting unnecessary libraries may also reduce exploitability, but this should not be treated as a substitute for patching.

Remediation

Patch, then assume compromise.

Upgrade OpenDJ Community Edition to version 5.1.1 or later, which addresses the unsafe deserialization condition in the JMX RMI connector. Validate that all affected deployments, including management interfaces and administrative nodes, are updated and that the vulnerable JMX exposure is no longer reachable in legacy configurations.

PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType

OpenIdentityPlatformOpendj-Server-Legacyapplication

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

ACTIVITY FEED

Recent activity

1 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.

1 SOURCESView more in app

No news coverage yet. Advisories and community discussion only.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.

Start free trial

Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity1