High [CVE-2026-15556] picketlink SAML 2.0 auth bypass via missing assertions
This high-severity Red Hat Linux advisory covers CVE-2026-15556 affecting Red Hat JBoss Enterprise Application Platform 7.
Android app · Google Play
Monitor future Red Hat Linux CVEs from your phone.
Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 32 official vendor sources and 160+ reviewed platform categories.
Summary
A flaw was found in Picketlink's SP signature validation; a SAML response containing zero assertion elements matching the signature check can allow an attacker to forge a SAML response and auth as any principal with any roles on the protected application. Red Hat JBoss EAP 8.x is not affected.
The vulnerable components (`picketlink-federation`, `picketlink-common`) are not shipped in EAP 8.x. The `org/picketlink/` module path does not exist.
The only PicketLink-related artifact in EAP 8.1 is `wildfly-picketlink-8.1.1.GA-redhat-00012.jar` — a WildFly subsystem extension that provides the `migrate` CLI operation for EAP 7→8 upgrades. This JAR contains no SAML processing code, no signature validation logic, and has no module dependency on `org.picketlink.federation`.
The PicketLink SAML SP code path is entirely absent from EAP 8.x. Red Hat severity: Important — CVSS 8.1 (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N).
Weakness: CWE-347. Affected Red Hat products: Red Hat JBoss Enterprise Application Platform 7.
Red Hat does not currently list a fixing RHSA for this CVE.
Affected versions
No affected-version range was extracted from the source record. The vendor advisory is authoritative — check it before change work.
Official advisory · medium-confidence parse· fetched 5 hours ago·verify at source
Fixed versions
No fixed release is recorded yet. That does not prove no patch exists — confirm against the vendor advisory.
Official advisory · medium-confidence parse· fetched 5 hours ago·verify at source
Mitigation
The source record does not include mitigation steps. That is not a statement that no fix exists — read the vendor advisory below for the authoritative guidance.
Official advisory · medium-confidence parse· fetched 5 hours ago·verify at source
Discussion(0)
No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.
Sign in to join the discussion.