OpenAM Pre-Authentication Deserialization Remote Code Execution

Open Access Management (OpenAM) is an access management solution. Prior to 16.1.2, the pre-authentication /authservice PLL endpoint accepts a CustomCallback XML element whose className value selects an arbitrary Java class for AuthXMLUtils to load and instantiate without verifying that it implements DSAMECallbackInterface. Default configurations expose the endpoint without authentication, allowing attacker-controlled class initialization and unsafe deserialization of a serialized Subject value to execute code in the server process. Enabling sunRemoteAuthSecurityEnabled does not prevent the vulnerable parsing and instantiation because its check occurs later. This issue is fixed in version 16.1.2.

Casky was already ahead

This CVE exploits attack patterns that Casky's 323matched skills already investigate — long before this vulnerability was disclosed. Claude's reasoning model maps these techniques to MITRE ATT&CK, so practitioners who ran these skills have already seen the threat behaviour in their findings.

Analysis

OpenAM versions prior to 16.1.2 contain a critical remote code execution vulnerability in the pre-authentication /authservice PLL endpoint. The flaw allows attackers to specify arbitrary Java classes through a CustomCallback XML element without proper validation, leading to unsafe deserialization and instantiation of untrusted code. Because this endpoint is exposed without authentication in default configurations, any network-accessible OpenAM instance becomes vulnerable to unauthenticated remote exploitation. Organizations relying on OpenAM for identity and access management face immediate risk of complete system compromise, as attackers can execute arbitrary code with the privileges of the OpenAM service.

Casky's 323 mapped skills detect this attack through Claude AI analysis of MITRE ATT&CK techniques TA0001 (Initial Access) and TA0043 (Reconnaissance). Practitioners using Casky would observe detection of suspicious XML payloads containing unexpected className attributes in /authservice requests, anomalous Java class instantiation patterns indicating CWE-94 (Improper Control of Generation of Code), and evidence of unsafe deserialization attempting to invoke non-interface implementations (CWE-470). The platform's extended reasoning capabilities correlate unauthenticated access attempts to sensitive pre-auth endpoints with XML-based injection patterns, flagging the specific attack chain and recommending immediate patching or network segmentation of OpenAM instances. Security teams gain visibility into both reconnaissance probing and exploitation attempts before code execution occurs.

Live Threat IntelligenceComing soon

Casky Risk Score

—

EPSS Probability

—

Shodan Exposure

—

GreyNoise Signal

—

Composite risk scoring from EPSS, CISA KEV, Shodan, and GreyNoise — 21 security APIs correlated into a single Casky Risk Score. Coming in Casky Pro. Join early access →

323 Casky skills cover this attack pattern

These skills use Claude AI's reasoning model to surface findings in the same attack categories as CVE-2026-62379.

Abuse of Public-Facing API: Mobile API Abuse

mobile security · low

Run

abusing-dpapi-for-credential-access

red teaming · high

Run

abusing-shadow-credentials-for-privesc

red teaming · high

Run

MITRE ATT&CK Techniques

TA0001 TA0043

Investigate the attack patterns behind CVE-2026-62379

Casky has 323 skills that investigate the attack patterns behind CVE-2026-62379. Run one and get CVSS-scored findings in 3 minutes.

Run the skill that detects this →

X Instagram LinkedIn