Executive Summary
A critical authentication bypass vulnerability has been disclosed in PicketLink Federation, a widely used Java-based SAML identity federation library. Tracked as CVE-2026-10579 with a CVSS score of 9.8, the flaw allows an unauthenticated remote attacker to authenticate as any user — including administrators — by submitting a forged SAML assertion that the unsolicited response handler accepts without verification.
Vulnerability Details
What Is PicketLink?
PicketLink is a Red Hat–sponsored open source security framework for Java applications. Its SAML federation module acts as a Service Provider (SP), enabling applications to delegate authentication to external Identity Providers (IdPs) such as Keycloak, Active Directory Federation Services, or Okta via the SAML 2.0 protocol.
The Flaw
The root cause is in the unsolicited response handler — the component responsible for processing SAML responses not triggered by a specific authentication request. This handler:
- Accepted SAML assertions without verifying the signature
- Did not validate the issuer or audience of the assertion
- Failed to check whether the response was actually solicited (replay protection bypass)
An attacker can craft a SAML response containing arbitrary identity claims and submit it directly to the SP endpoint. Because no verification occurs, the forged assertion is accepted as legitimate, granting the attacker full access as the impersonated identity.
Impact
| Metric | Value |
|---|---|
| CVSS Score | 9.8 (Critical) |
| Attack Vector | Network |
| Authentication Required | None |
| Confidentiality Impact | High |
| Integrity Impact | High |
| Availability Impact | High |
All three pillars of the CIA triad are fully compromised. An attacker gaining access as an administrative account could exfiltrate sensitive data, modify application state, or pivot to downstream systems.
Affected Products
- PicketLink Federation — all versions with the unsolicited SAML response handler enabled
- Applications using PicketLink as the SAML SP layer (common in legacy JBoss/WildFly deployments)
- Red Hat JBoss Enterprise Application Platform deployments with SAML SSO configured
Exploitation Risk
The vulnerability is trivially exploitable. SAML authentication bypass flaws are well-understood by attackers — tooling for crafting forged SAML assertions is publicly available, and the attack requires no credentials or special access. The attack surface is any endpoint that accepts SAML responses from external IdPs.
Organizations running PicketLink in SSO flows for internal or customer-facing applications should treat this as an active exploitation risk.
Remediation
- Apply the vendor patch — Update PicketLink to the patched version that enforces signature verification on all SAML responses, including unsolicited ones.
- Audit SAML configuration — Ensure
WantAssertionsSignedis set totruein your SP metadata and that the IdP is configured to sign all assertions. - Review access logs — Check for any unusual authentication events, particularly logins from unknown IP addresses or outside normal business hours.
- Restrict SP endpoints — If possible, apply network-level controls to limit which IP ranges can submit SAML responses.
- Consider migration — PicketLink has had limited upstream maintenance activity. Organizations relying on it for critical SSO flows should evaluate migration to actively maintained alternatives such as Spring Security SAML, Pac4j, or Keycloak as the SP.
SAML Security Hardening Checklist
- SAML assertions signed by IdP (
WantAssertionsSigned: true) - SAML responses signed by IdP (
WantResponseSigned: true) - Audience restriction enforced (assertion's
Audiencematches SP entity ID) -
NotBefore/NotOnOrAftertime conditions validated -
InResponseToattribute checked against outstanding AuthnRequests (replay protection) - Single-use enforcement for
AssertionID(prevent assertion replay) - Clock skew bounded to ≤ 5 minutes
- IdP metadata pinned and verified via trusted configuration