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

Back
New CVE Detected

CVE-2026-62379 – Unauthenticated Remote Code Execution – OpenAM ≤ 16.1.1

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

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-62379 is a critical unauthenticated remote code execution vulnerability in OpenAM, an open-source access management platform. The flaw resides in the pre-authentication /authservice (PLL) endpoint, where XML requests containing a CustomCallback element allow an attacker to specify arbitrary Java class names that the server loads and instantiates without validation. It carries a CVSS v3.1 base score of 9.8 (Critical) and is reachable over the network without credentials or user interaction.

Technical details

  • Root cause: the /authservice endpoint parses incoming XML and, via AuthXMLUtils.createCustomCallback, uses Class.forName to load a class name supplied in the CustomCallback element before verifying that the class implements the expected DSAMECallbackInterface.
  • Class loading and instantiation occur during XML parsing, ahead of any authentication or input-validation checks, allowing static initializers and constructors of attacker-chosen classes to execute in the server process.
  • Trigger conditions: sending a crafted XML request containing a CustomCallback element with an attacker-controlled class name to the /authservice endpoint; exploitable in default configurations with no authentication required.
  • Attack vector: network, low attack complexity, no privileges or user interaction required.
  • Impact: full compromise of confidentiality, integrity, and availability of the OpenAM server, since the vulnerability enables execution of arbitrary code in the server process.
  • Weakness classification: CWE-94 (Improper Control of Generation of Code) and CWE-470 (Use of Externally-Controlled Input to Select Classes or Code / unsafe reflection).

Affected software

  • OpenAM (Open Identity Platform fork) versions up to and including 16.1.1

Severity

  • CVSS v3.1 Base Score: 9.8 (Critical)
  • Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Mitigation and recommended actions

  • Immediate: Upgrade OpenAM to version 16.1.2 or later, which resolves the class name to a resource without executing static initializers and restricts instantiation to classes implementing DSAMECallbackInterface.
  • If patching is not immediately possible: restrict network access to the /authservice endpoint to trusted networks only, place a web application firewall or reverse proxy in front of OpenAM to block requests containing unexpected CustomCallback XML elements, and monitor authentication service logs for anomalous or malformed authentication XML payloads until the patch can be applied.

References

Are you exposed?

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

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

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

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

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

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge