CVE-2026-63182: litesaml/lightsaml · lightsaml allows Signature wrapping bypass
Affects litesaml/lightsamlSource GCVE Database
Not known to be exploited · CVSS 8.1 High : upgrade to 5.0.1 soon.
Data as of 16 Nov 2026, 23:12 UTC
Thin evidence
One scorer or none| CNA (GitHub_M) | CVSS 3.1 | 8.1 |
|---|
- Patch
- Available – fixed in 5.0.1, 4.7.1
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:NExploitation evidence
Disclosed: evidence found.
CVE published 30 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 16 Nov 2026.
What to do
Upgrade litesaml/lightsaml to 5.0.1; litesaml/lightsaml to 4.7.1.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Packagistlitesaml/lightsaml | Affected
| Fixed in
|
| Packagistlitesaml/lightsaml | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A patch is available and should be applied. The issue is fixed in LightSaml versions 4.7.1 and 5.0.1. Users should upgrade to these or later versions to remediate the vulnerability. No alternative mitigations or workarounds are documented. Since this is a library vulnerability, applying the official fix is the recommended action.
Description
LightSaml versions 4.6.1 through 5.0.0 contain a signature validation flaw allowing signature wrapping bypass. The vulnerability arises because LightSaml collects direct-child assertions for validation, but the underlying XML signature library (xmlseclibs) validates the signature against the first ID-bearing element in the entire document, which may differ. This discrepancy enables an attacker to present a forged assertion with attacker-controlled claims that appear signed by reusing a genuine signature from a buried assertion element. The issue is fixed in LightSaml versions 4.7.1 and 5.0.1.
References
- github.com/litesaml/lightsaml/security/advisories/GHSA-w553-pwx6-3mg9 (opens in a new tab)
- nvd.nist.gov/vuln/detail/CVE-2026-63182 (opens in a new tab)
- github.com/litesaml/lightsaml/pull/113 (opens in a new tab)
- github.com/litesaml/lightsaml/pull/122 (opens in a new tab)
- github.com/litesaml/lightsaml/commit/230e62d1325f2cbcaac814b78409775f7a8806a2 (opens in a new tab)
- github.com/litesaml/lightsaml/commit/3af82bf2f3865e6aafeeb1a97c97b383b8bb7b00 (opens in a new tab)
- github.com/litesaml/lightsaml (opens in a new tab)
- github.com/litesaml/lightsaml/releases/tag/4.7.1 (opens in a new tab)
- github.com/litesaml/lightsaml/releases/tag/5.0.1 (opens in a new tab)