Skip to content

OpenAM: Unauthenticated Remote Code Execution via Class.forName in AuthXMLUtils.createCustomCallback

Critical severity GitHub Reviewed Published Jul 23, 2026 in OpenIdentityPlatform/OpenAM • Updated Jul 24, 2026

Package

maven org.openidentityplatform.openam:openam-core (Maven)

Affected versions

<= 16.1.1

Patched versions

16.1.2

Description

Summary

A pre-authentication remote code execution vulnerability affects OpenAM. The
remote authentication endpoint (/authservice, PLL) accepts an XML element
that names an arbitrary Java class, which the server then loads and
instantiates without validation. On a default configuration this is reachable
without authentication and allows an attacker to run code on the server.

Impact

Unauthenticated remote code execution / full server compromise on any OpenAM
instance with default settings.

Affected

All releases up to and including 16.1.1 (the defect predates the Open Identity
Platform fork).

Remediation

Upgrade to 16.1.2.

Interim mitigation

  • Require the remote-auth security token by enabling
    sunRemoteAuthSecurityEnabled (rejects unauthenticated /authservice calls).
  • Restrict or block external network access to /authservice until patched.

Credit

Vulnerability discovered by Zhixi "Jace" Sun of ASM/VI at TikTok.

References

@vharseko vharseko published to OpenIdentityPlatform/OpenAM Jul 23, 2026
Published to the GitHub Advisory Database Jul 24, 2026
Reviewed Jul 24, 2026
Last updated Jul 24, 2026

Severity

Critical

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

EPSS score

Weaknesses

Improper Control of Generation of Code ('Code Injection')

The product constructs all or part of a code segment using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the syntax or behavior of the intended code segment. Learn more on MITRE.

Use of Externally-Controlled Input to Select Classes or Code ('Unsafe Reflection')

The product uses external input with reflection to select which classes or code to use, but it does not sufficiently prevent the input from selecting improper classes or code. Learn more on MITRE.

CVE ID

CVE-2026-62379

GHSA ID

GHSA-wg5r-wc3x-39vc

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.