CVE-2026-62379 is a critical-severity (CVSS 9.8) remote code execution vulnerability in org.openidentityplatform.openam:openam-core. O3 Security confirms whether CVE-2026-62379 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
OpenAM: Unauthenticated Remote Code Execution via Class.forName in AuthXMLUtils.createCustomCallback
Real-World Exposure
org.openidentityplatform.openam:openam-coreReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
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. 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.
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.openidentityplatform.openam:openam-core | all versions | 16.1.2 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.openidentityplatform.openam:openam-core. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update org.openidentityplatform.openam:openam-core to 16.1.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-62379 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether CVE-2026-62379 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to CVE-2026-62379. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2026-62379 in your dependencies?
O3 detects CVE-2026-62379 across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.