PicketLink EUVD-2026-55980

Exploitation requires that the target application uses PicketLink for SAML SSO and has the unsolicited (IdP-initiated) SAML response flow enabled/reachable - the description explicitly scopes the flaw to the 'unsolicited response handler,' which is the concrete precondition. The attacker needs network access to the SP's assertion consumer endpoint but no credentials, no user interaction, and no valid IdP signing key, since forged assertions are accepted without verification. Limiting factors: deployments that only permit strictly SP-initiated flows, that terminate SAML validation at an upstream gateway, or that do not expose the unsolicited endpoint reduce or remove exposure; the deprecated status of PicketLink also narrows the realistic target population.

The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H, base 9.8) is internally consistent with the description: a network-facing SSO endpoint, no authentication and no user interaction required, low complexity because forging and POSTing a SAML assertion needs no special timing or race, and complete compromise of confidentiality, integrity, and availability through full identity spoofing. No EPSS score, KEV entry, POC, or SSVC decision data was supplied, so probabilistic exploitation signals cannot be weighed - the assessment rests on the CVSS vector and description alone. This is a genuine priority rather than a high-CVSS-but-low-real-risk case, because authentication bypasses are directly and reliably exploitable; however, real-world exposure is bounded by how widely PicketLink SAML SSO is still deployed, since the framework is deprecated. Note: exploitability depends on the affected application actually enabling the unsolicited/IdP-initiated response flow - verify configuration with the vendor.

An attacker crafts a SAML Response containing an assertion that names a privileged user (for example an administrator) and POSTs it directly to the PicketLink Service Provider's assertion consumer endpoint as an unsolicited response. Because the handler performs no signature verification or validation, the SP establishes an authenticated session as that user, granting the attacker their roles and access. No prior credentials, user interaction, or authentication are required (AV:N/AC:L/PR:N/UI:N); no public POC is currently identified.