Skip to main content
VulnerabilityPublished

CVE-2026-63182: litesaml/lightsaml · lightsaml allows Signature wrapping bypass

Affects litesaml/lightsamlSource GCVE Database

0
Compare
Authoritative record:CVE-2026-63182· High 8.1

Not known to be exploited · CVSS 8.1 High : upgrade to 5.0.1 soon.

Data as of 16 Nov 2026, 23:12 UTC

CVSS 3.1 base score
8.1High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (GitHub_M)CVSS 3.18.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:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 30 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

ProductAffectedFixed in
Packagistlitesaml/lightsamlAffected
  • >=5.0.0 <5.0.1
Fixed in
  • 5.0.1
Packagistlitesaml/lightsamlAffected
  • >=4.0.0 <4.7.1
Fixed in
  • 4.7.1

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

Community reviews

Loading reviews…