CVE-2026-46623 OpenIdentityPlatform CVE debrief

Who should care

Defenders responsible for OpenAM deployments, identity and access management, and OAuth2 authentication should assess exposure and prioritize verification and remediation. This includes operators, platform administrators, vulnerability management teams, and security teams who need to verify OpenAM version and exposure, and implement compensating controls for account creation and OAuth login.

Why it matters

CVE-2026-46623 allows unauthenticated attackers to take over local accounts in OpenAM instances with account creation enabled, requiring defenders to verify and upgrade to version 16.1.1.

• Unauthenticated attackers can take over local accounts without interacting with the identity provider
• Account creation enabled allows repeated OAuth login to accept username as both identifier and password
• Rewritten password can be denied for usernames shorter than the configured minimum password length
• Verification of OpenAM version and exposure is necessary to prevent account takeover

Technical summary

The OpenAM OAuth2 authentication module updates existing local accounts with profile attributes, including userPassword and inetUserStatus, allowing an unauthenticated attacker to take over the local account without interacting with the identity provider. This occurs when account creation is enabled, and repeated OAuth login accepts the username as both identifier and password. The rewrite can be denied for usernames shorter than the configured minimum password length. Defenders should prioritize verifying and upgrading to version 16.1.1, assessing exposure of OpenAM instances, and implementing compensating controls for account creation and OAuth login.

Defensive priority

Defenders should prioritize verifying and upgrading to version 16.1.1, assessing exposure of OpenAM instances, and implementing compensating controls for account creation and OAuth login.

Recommended defensive actions

• Verify OpenAM version and upgrade to 16.1.1 if necessary
• Assess exposure of OpenAM instances to unauthenticated attackers
• Implement compensating controls for account creation and OAuth login
• Monitor for suspicious account activity and OAuth login attempts
• Review relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The CVE record and NVD entry provide details on the vulnerability, but evidence is limited regarding actual exploitation and affected deployments. Defenders should verify OpenAM version and exposure, and implement compensating controls for account creation and OAuth login. The CVE Program record and NVD detail page offer source-provided CVE metadata and vulnerability assessment. However, additional verification tasks are necessary to confirm affected scope and severity.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.