CVE-2026-63182 with a CVSS score of 8.1 is a signature wrapping bypass in LightSaml SAML response processing affecting litesaml/lightsaml (composer) versions >= 5.0.0, < 5.0.1 and litesaml/lightsaml (composer) versions >= 4.0.0, < 4.7.1. The flaw occurs when an inbound samlp:Response is validated: LightSaml collects direct-child saml:Assertion elements and reads claims from them, while the delegated XML signature validation resolves a Reference URI by selecting the first ID-bearing element anywhere in the document. A remote attacker with low privileges and a captured genuine signed assertion can craft a response that buries the genuine signed bytes in samlp:Extensions and presents a forged direct-child assertion carrying a copied signature and attacker-controlled claims. Because the signature check validates the buried element while LightSaml consumes the forged element, the forged assertion is accepted as signed by the trusted identity provider. This enables authentication bypass and privilege escalation, allowing attacker-authored subject, condition, and attribute claims to be treated as authentic, with high confidentiality and integrity impact and no availability impact.
We recommend you to update LightSaml to version 5.0.1 or 4.7.1 depending on your installed branch.[/subscribe_to_unlock_form]
CVE-2026-63182 with a CVSS score of 8.1 is a signature wrapping bypass in LightSaml SAML response processing affecting litesaml/lightsaml (composer) versions >= 5.0.0, < 5.0.1 and litesaml/lightsaml (composer) versions >= 4.0.0, < 4.7.1. The flaw occurs when an inbound samlp:Response is validated: LightSaml collects direct-child saml:Assertion elements and reads claims from them, while the delegated XML signature validation resolves a Reference URI by selecting the first ID-bearing element anywhere in the document. A remote attacker with low privileges and a captured genuine signed assertion can craft a response that buries the genuine signed bytes in samlp:Extensions and presents a forged direct-child assertion carrying a copied signature and attacker-controlled claims. Because the signature check validates the buried element while LightSaml consumes the forged element, the forged assertion is accepted as signed by the trusted identity provider. This enables authentication bypass and privilege escalation, allowing attacker-authored subject, condition, and attribute claims to be treated as authentic, with high confidentiality and integrity impact and no availability impact.
We recommend you to update LightSaml to version 5.0.1 or 4.7.1 depending on your installed branch.[emaillocker id="1283"]
The following reports contain further technical details:
[/emaillocker]