Multiple SAML libraries may allow authentication bypass via incorrect XML canonicalization and DOM traversal

published 2019-04-17 7 y ago modified 2026-06-17 4 mo ago also GHSA-5p5w-j3g7-w4wv , EUVD-2019-0579

cvss: 7.7; version 3.0, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 2.7%; EPSS 2.7% chance of exploitation in 30 days, percentile 86%
public exploits: 0; none known

Clever saml2-js 2.0 and earlier may incorrectly utilize the results of XML DOM traversal and canonicalization APIs in such a way that an attacker may be able to manipulate the SAML data without invalidating the cryptographic signature, allowing the attack to potentially bypass authentication to SAML service providers.

Patch / fix

fixed in 2

npm saml2-js 1.12.4, 2.0.2
Clever saml2-js 1.0, 2.0

Exploit prediction

2.75% chance of exploitation in the next 30 days, higher than 86% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

duo.com https://duo.com/blog/duo-finds-saml-vulnerabilities-affecting-multiple-implementations referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by	version	score	vector
CNA	3.0	7.7	CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N
NVD	3.0	9.8	CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD	2.0	7.5	AV:N/AC:L/Au:N/C:P/I:P/A:P
GitHub	3.0	7.7	CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N

Affected packages

ecosystem	package	affected	fixed in
npm	saml2-js	<1.12.4 >=2.0.0, <2.0.2	1.12.4 2.0.2

Affected products

Clever saml2-js

Classification

Weakness

CWE-287 Improper Authentication

References

duo.com /blog/duo-finds-saml-vulnerabilities-affecting-multiple-implementations
web, exploit, technical-description, third-party-advisory
kb.cert.org /vuls/id/475445
web, third-party-advisory, us-government-resource
nvd.nist.gov /vuln/detail/CVE-2017-11429
advisory
github.com /advisories/GHSA-5p5w-j3g7-w4wv
advisory
npmjs.com /advisories/567
web

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

Summary