Multiple security vulnerabilities have been identified in the SAML2 library, affecting the HTTP-Artifact binding in version ranges 6.2.2 through 6.2.3 and 7.0.0-rc1 and later pre-release versions before the next release. The issues can allow an attacker who controls a trusted identity provider in a federation to bypass authentication controls. This creates a high risk of cross-identity-provider impersonation and unauthorized access.
CVE-2026-110782 (CVSS 8.7 — High): A signature-verification gap in the HTTP-Artifact binding allows an unsigned embedded SAML response to be accepted when the outer artifact response is signed by a trusted identity provider. An attacker controlling one trusted provider can forge a response that claims to come from another provider, enabling cross-provider authentication bypass.[/subscribe_to_unlock_form]
Multiple security vulnerabilities have been identified in the SAML2 library, affecting the HTTP-Artifact binding in version ranges 6.2.2 through 6.2.3 and 7.0.0-rc1 and later pre-release versions before the next release. The issues can allow an attacker who controls a trusted identity provider in a federation to bypass authentication controls. This creates a high risk of cross-identity-provider impersonation and unauthorized access.
CVE-2026-110782 (CVSS 8.7 — High): A signature-verification gap in the HTTP-Artifact binding allows an unsigned embedded SAML response to be accepted when the outer artifact response is signed by a trusted identity provider. An attacker controlling one trusted provider can forge a response that claims to come from another provider, enabling cross-provider authentication bypass.[emaillocker id="1283"]
CVE-2026-49283 (CVSS 8.7 — High): A TLS validator confusion in the HTTP-Artifact binding allowed signature verification to use the wrong identity provider metadata. An attacker in a multi-provider federation could exploit the confusion to bypass cross-provider authentication controls.
These vulnerabilities collectively present a high risk to service providers that use the HTTP-Artifact binding in multi-identity-provider federations. The most exposed deployments are those where a single trusted provider can issue artifact responses for other providers. Organizations should assess their exposure and treat affected deployments as requiring urgent review.
We recommend you to update simplesamlphp/saml2 to version 6.2.4 or 7.0.0-rc2 depending on your installed branch.
The following reports contain further technical details:
[/emaillocker]