External risk intelligence

OpenAM WebAuthn Deserialization Gadget Found

CVE advisorySeverity: CRITICAL (CVSS 9.2)

CVE-2026-62263

Open Access Management (OpenAM) is an identity and access management solution. These platforms are designed to be public-facing to handle user authentication, identity portals, and access control services, making them inherently internet-reachable in common deployments.

Deserialization

Halo Surface Signal: 5 out of 5 — more likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

This advisory addresses a critical vulnerability in Open Access Management (OpenAM), a solution for managing user access. The issue involves a flaw in how certain data is processed, which could allow an unauthenticated attacker to potentially execute malicious code. This bypasses previous security measures and impacts systems running versions prior to 16.1.2.

  • Flaw allows code execution before authentication.
  • Affects access management solutions, potentially public-facing.
  • Confirm relevance and exposure of this access management flaw.

Attack Path

How an attacker could exploit the issue

An attacker could target the Open Access Management (OpenAM) system through its network interface, requiring only partial authentication to reach the vulnerable component. By crafting a specific serialized object, the attacker can trigger a deserialization vulnerability within the WebAuthn authentication process. This bypasses earlier security measures and can lead to arbitrary code execution if a malicious gadget is present on the system's classpath.

  • Requires partial authentication and network access.
  • Triggered by deserializing a malicious user handle.
  • Risks code execution before verification.

Live Threat

Current exploitation, exposure, and threat context

A pre-authentication attacker could exploit this vulnerability by supplying specially crafted data during the deserialization process. When supported by the advisory's conditions, this could lead to the execution of arbitrary code on the affected system before proper verification, potentially impacting the integrity and availability of the access management solution.

  • System data and service integrity at risk.
  • Unauthenticated network input could trigger it.
  • Compromised access control and service availability.

Operational Fix

Recommended remediation, mitigation, and detection steps

Ownership of this vulnerability likely falls to the platform or infrastructure teams responsible for managing the OpenAM access management solution, with input from security teams for exposure assessment and vendor management for coordination. The first practical step is to identify all OpenAM instances, determine their reachability and business criticality, and then engage the accountable owner to plan remediation based on the assessed risk.

  • Platform and infrastructure teams own the issue.
  • Verify OpenAM instances and their exposure.
  • Plan remediation, potentially involving vendor coordination.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is Open Access Management (OpenAM)?

OpenAM is an identity and access management software suite used by organizations to handle authentication, identity portals, and centralized access control for users. It functions as a security gateway, managing how people sign in and access various services, which makes it a central component of an organization's digital infrastructure.

What is the vulnerability in CVE-2026-62263?

This CVE involves deserialization of untrusted data, classified as CWE-502. The software fails to properly filter serialized objects during WebAuthn authentication. By supplying a specially crafted object, an attacker can trick the system into executing malicious code hidden within that object's structure before the system has verified the user's identity.

How is this vulnerability triggered?

An attacker triggers the bug by sending a specifically crafted user handle to the WebAuthn authentication process. The flaw specifically allows the system to process nested objects that were meant to be restricted. Note that this requires the presence of a usable gadget class on the system's classpath to achieve code execution; simply interacting with the service without such a payload does not trigger the flaw.

Do I need to worry about this if my server is internal?

Halo Surface Signal indicates that OpenAM platforms are often public-facing because they provide essential authentication and identity portals for users. While internet-facing instances are at higher risk, any deployment of OpenAM that processes network requests, even within internal networks, remains a potential target if an attacker gains access to those segments.

What are the first steps to address this issue?

Begin by auditing your environment to locate all running instances of OpenAM and confirm their current version. If you are running any version prior to 16.1.2, you are affected. Coordinate with your infrastructure and platform teams to schedule an update to version 16.1.2, which contains the fix for this deserialization logic.

References