Summary
OpenAM: Unauthenticated Remote Code Execution via Class.forName in AuthXMLUtils.createCustomCallback
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.
Affected
All releases up to and including 16.1.1 (the defect predates the Open Identity
Platform fork).
Interim mitigation
If you cannot upgrade immediately:
- Restrict or block external network access to
/authservice. This is the
only reliable mitigation. - Optionally, block PLL requests carrying a
<CustomCallback className="...">
element at the reverse proxy or WAF. That element is only produced for customDSAMECallbackInterfacecallbacks, so most deployments never send it, confirm
against your own traffic before enforcing. - Enabling
sunRemoteAuthSecurityEnableddoes not mitigate this issue. The
remote-auth security token is checked inAuthXMLHandler.processAuthXMLRequest,
which runs only afterAuthXMLRequest.parseXMLhas already parsed the request
and instantiated the class named in the<CustomCallback className="...">
element. Do not rely on it as a substitute for upgrading or for network
restriction.
Credit
Vulnerability discovered by Zhixi "Jace" Sun of ASM/VI at TikTok.
Correction of the interim mitigation guidance contributed by @BarakSrour.
Impact
Unauthenticated remote code execution / full server compromise on any OpenAM
instance with default settings.
Untrusted input is evaluated as executable code within the application's runtime environment. Typical impact: arbitrary code execution within the application's privilege context.
CVE-2026-62379 has a CVSS score of 9.8 (Critical). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (16.1.2); upgrading removes the vulnerable code path.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
Upgrade to 16.1.2. The fix resolves the class named in a <CustomCallback>
element without running its static initialisers and rejects it unless it
implements DSAMECallbackInterface, and it constrains deserialisation of the
serialised Subject value to a class allowlist.
Frequently Asked Questions
- What is CVE-2026-62379? CVE-2026-62379 is a critical-severity code injection vulnerability in org.openidentityplatform.openam:openam-core (maven), affecting versions <= 16.1.1. It is fixed in 16.1.2. Untrusted input is evaluated as executable code within the application's runtime environment.
- How severe is CVE-2026-62379? CVE-2026-62379 has a CVSS score of 9.8 (Critical). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
- Which versions of org.openidentityplatform.openam:openam-core are affected by CVE-2026-62379? org.openidentityplatform.openam:openam-core (maven) versions <= 16.1.1 is affected.
- Is there a fix for CVE-2026-62379? Yes. CVE-2026-62379 is fixed in 16.1.2. Upgrade to this version or later.
- Is CVE-2026-62379 exploitable, and should I be worried? Whether CVE-2026-62379 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2026-62379 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2026-62379? Upgrade
org.openidentityplatform.openam:openam-coreto 16.1.2 or later.