Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

New CVE Detected

CVE-2026-105115 – Unauthenticated Arbitrary Class Instantiation / Potential RCE – OpenAM ≤ 16.1.2

Be the first to know when new zero-days emerge:

Summary

CVE-2026-105115 is a missing authentication vulnerability in OpenAM’s legacy JAX-RPC SOAP interface (/jaxrpc/*) that allows an unauthenticated, network-based attacker to load and instantiate arbitrary Java classes available on the server’s classpath. The flaw affects all OpenAM versions through 16.1.2 and carries a High/Critical severity rating given its unauthenticated, network-exploitable nature and potential for server crashes, classpath enumeration, or code execution.

Technical details

  • Root cause: the legacy JAX-RPC SOAP endpoint takes a Java class name directly from the incoming request and loads/instantiates it before verifying that it is of the expected type (CWE-470, Unsafe Reflection with External Input).
  • Compounding issue: the operation performs inadequate session validation, accepting session identifiers without actually verifying them (CWE-306, Missing Authentication for Critical Function).
  • Trigger conditions: an attacker sends a crafted SOAP request to an exposed /jaxrpc/* endpoint, supplying an arbitrary class name and an unverified session identifier — no authentication or prior access is required.
  • Attack vector: network-based, no privileges or user interaction needed.
  • Impact: confirmed impacts include denial of service (server crashes) and classpath/class enumeration; the advisory states the theoretical ceiling is remote code execution via gadget chains, though RCE has not been publicly demonstrated.

Affected software

  • OpenIdentityPlatform OpenAM versions ≤ 16.1.2 (all versions prior to 16.1.3)

Severity

  • CVSS v3.1 Base Score: 8.6 (High) — CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:H
  • A CVSS v4.0 score of 8.8 (High) has also been published for this CVE.

Mitigation and recommended actions

  • Immediate: Upgrade to OpenAM 16.1.3 or later, which contains the fix for this issue.
  • If immediate patching is not possible: Restrict network access to the /jaxrpc/* path at the firewall or reverse-proxy level; if legacy remote SDK clients that depend on the JAX-RPC interface are not in use, block access to this path entirely.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge