Is there a public PoC exploit available for CVE-2026-45052?

Yes, a public proof-of-concept exploit is available for CVE-2026-45052. Prioritise patching immediately. EPSS: 0.6%.

Is there a patch available for CVE-2026-45052?

Yes, a patch is available for CVE-2026-45052. Update the affected software to the latest version immediately.

OpenAM's Liberty Web Services SOAP CVE-2026-45052

Q: What is the CVSS score of CVE-2026-45052?

CVE-2026-45052 has a CVSS 4.0 base score of 9.3 (Critical). CVSS vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:L/SC:N/SI:L/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X. EPSS exploitation probability: 0.6%.

EUVD-2026-78352 CRITICAL

Improper Authorization (CWE-285)

2026-06-24 https://github.com/OpenIdentityPlatform/OpenAM

GHSA-p462-xxwx-pqf4

Authentication Bypass

9.3

CVSS 4.0 · Vendor: https://github.com/OpenIdentityPlatform/OpenAM

Severity by source

Vendor (https://github.com/OpenIdentityPlatform/OpenAM) PRIMARY

9.3 CRITICAL

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:L/SC:N/SI:L/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

vuln.today AI

7.5 HIGH

Unauthenticated network SOAP write reachable in defaults gives AV:N/AC:L/PR:N/UI:N; impact is a persistent integrity write (I:H) with no read or availability loss (C:N/A:N), scope unchanged as it stays within the LDAP identity store.

3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

4.0 AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (https://github.com/OpenIdentityPlatform/OpenAM).

CVSS VectorVendor: https://github.com/OpenIdentityPlatform/OpenAM

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Lifecycle Timeline

Analysis Updated

Sep 15, 2026 - 10:31 vuln.today

v2 (cvss_changed)

Re-analysis Queued

Sep 15, 2026 - 10:22 vuln.today

cvss_changed

CVSS changed

Sep 15, 2026 - 10:22 NVD

9.3 (CRITICAL)

Source Code Evidence Fetched

Jun 24, 2026 - 17:50 vuln.today

Analysis Generated

Jun 24, 2026 - 17:50 vuln.today

Blast Radius

ecosystem impact

† from your stack dependencies † transitive graph · vuln.today resolves 4-path depth

8 maven packages depend on org.openidentityplatform.openam:openam-federation-library (5 direct, 3 indirect)

Ecosystem-wide dependent count for version 16.1.1.

DescriptionCVE.org

Summary

Description

An Improper Authorization (CWE-285) issue in OpenAM's Liberty Web Services SOAP receiver allows an unauthenticated remote attacker to write persistent entries into the Liberty Discovery store on any user's LDAP entry, and into a shared root-realm Discovery branch. This impacts OpenAM Community Edition through version 16.0.6. This issue was patched in version 16.1.1.

Liberty ID-WSF is a legacy protocol superseded by SAML 2.0, OAuth, and OIDC, and deployments that intentionally leverage it assume the risks of an unmaintained federation stack. While Liberty is exposed in the shipped defaults, this bug does not require active Liberty consumers for the write itself. Downstream impact depends on whether anything consumes Discovery data. The endpoint accepts anonymous writes that are performed server-side by the Discovery handlers, bypassing the requester's LDAP and identity ACLs. The global Discovery path explicitly uses the internal admin token.

Impact

OpenAM Community Edition deployments through version 16.0.6 that expose the Liberty Web Services component are potentially affected. An unauthenticated attacker who can reach the relevant endpoint may write persistent records to the discovery store, bypassing normal identity-layer access controls.

These writes are performed with elevated internal privileges server-side. In deployments that actively consume Liberty discovery data, manipulated records could influence service routing or security mechanism selection in subsequent requests. The severity of downstream impact varies by deployment..

Patch

This has been patched in OpenAM Community Edition version 16.1.1. Users are encouraged to update to the latest release.

AnalysisAI

We need produce JSON per schema. Need analyze all data. Let's parse input carefully.

CVE-2026-45052. Description summary: Improper Authorization CWE-285 in OpenAM's Liberty Web Services SOAP receiver allows unauthenticated remote attacker to write persistent entries into Liberty Discovery store on any user's LDAP entry and shared root-realm Discovery branch. Impact OpenAM Community Edition through 16.0.6. Patched 16.1.1. Liberty legacy, exposed in shipped defaults, no active Liberty consumers required for write. Endpoint accepts anonymous writes performed server-side by Discovery handlers bypassing requester's LDAP/identity ACLs. Global Discovery path uses internal admin token. Downstream depends on consuming discovery.

CVSS Score: 9.3, Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:L/SC:N/SI:L/SA:N/E:X/CR:X... many X. We need perhaps assess independently. Input CVSS 4.0 indicates AV:N, AC:L, AT:N, PR:N, UI:N, VC:H, VI:H, VA:L, SC:N, SI:L, SA:N. E:X etc. It gives score 9.3? For 4.0 likely 9.3? okay.

CWE CWE-285.

EPSS 0.55% percentile 45%. Low. POC/Exploit publicly available. Patch available from vendor. Reported by GitHub. CPE pkg:maven/org.openidentityplatform.openam:openam-federation-library. Tags: Authentication Bypass. ENISA EUVD ID. Affected versions EUVD: OpenAM <16.1.1. References: nvd none commit, releases tag 16.1.1, cve-search exploit gist, gh advisory.

Source code evidence: Docs commit diff. Important: The code diff reveals endpoints Liberty disabled by default? Wait description says exposed in shipped defaults, but patch commit diff adds documentation saying endpoint disabled by default with property com.sun.identity.liberty.enabled=false. But this might be the patch behavior, not pre-patch. The advisory says "While Liberty is exposed in shipped defaults" meaning before patch? The patch adds kill-switch default false. So perhaps affected versions shipped with Liberty enabled? Need reconcile. The documentation diff is part of patch; says endp