CVE-2026-105115 OpenIdentityPlatform CVE debrief

Who should care

Defenders responsible for OpenAM deployments should assess exposure and apply patches or mitigations. This includes operators, platform administrators, vulnerability management teams, and security teams who need to verify exposure and apply patches or mitigations to prevent potential server crashes, classpath probing, and code execution. OpenAM deployments should be reviewed for exposure, and patches or mitigations should be applied as soon as possible to

Why it matters

CVE-2026-105115 is a high-severity vulnerability in OpenAM that allows unauthenticated arbitrary class instantiation. Defenders should prioritize verifying exposure and applying patches or mitigations to prevent potential server crashes, classpath probing, and code execution.

• Potential server crashes via crafted SOAP requests
• Possible classpath probing via SOAP requests
• Potential code execution via gadget chains

Technical summary

The vulnerability allows remote attackers to load classes without authentication via the legacy JAX-RPC SOAP interface in OpenAM before version 16.1.3. This can lead to server crashes, classpath probing, and potentially code execution via gadget chains. The vulnerability exists due to the lack of authentication in the JAX-RPC SOAP interface, allowing attackers to send SOAP requests to /jaxrpc/* with an unverified session identifier and a chosen class name. Defenders should prioritize verifying exposure and applying patches or mitigations to prevent potential impacts.

Defensive priority

Defenders should prioritize verifying exposure and applying patches or mitigations.

Recommended defensive actions

• Verify OpenAM version and exposure to the JAX-RPC SOAP interface
• Apply patches or mitigations for OpenAM version 16.1.3 or later
• Monitor for suspicious SOAP requests to /jaxrpc/*
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The CVE record and NVD entry provide details on the vulnerability, but additional information on affected versions and remediation is limited. The legacy JAX-RPC SOAP interface in OpenAM before version 16.1.3 allows unauthenticated arbitrary class instantiation. Defenders should verify exposure and apply patches or mitigations. The CVE Program record and NVD detail page offer source-provided CVE metadata and vulnerability assessments. However, further details on affected scope and vendor guidance are needed for comprehensive risk and

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.