Tngan samlify
samlify: XML Injection in AttributeValue Allows Privilege Escalation in Signed SAML Assertions
samlify is a Node.js library for SAML single sign-on. Prior to version 2.13.0, samlify’s template substitution only escapes attribute contexts. Values inserted into element text (e.g., <saml:AttributeValue>) are not escaped. A normal user can inject XML markup into an attribute value (e.g., email, name) and add new <saml:Attribute> elements inside the signed assertion. The IdP then signs the tampered assertion and the SP accepts the injected attributes as trusted. This allows privilege escalation when attributes are used for authorization (roles/groups). This issue has been patched in version 2.13.0.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- < 2.13.0
Fixed in 2.13.0
Mitigation
Upgrade samlify to 2.13.0 or later.
References
- Vendor advisory github.com/tngan/samlify/security/advisories/G…
Timeline
Days relative to CVE publicationFirst public PoC 22 days after publication; not in CISA KEV. First PoC: BiiTts/CVE-2026-46490-samlify-SAML-Attribute-Injection (created 30 Jun 2026, found by us: backfilled).
PoC repositories
Found on GitHub.1 PoCs
PoCs 1
| Repository | Created | Stars | Assessment |
|---|---|---|---|
| BiiTts/CVE-2026-46490-samlify-SAML-Attribute-Injection | 30 Jun 2026 +22 d | 0 | PoC via PoC Index |
Only PoCs count toward the first-PoC date and the characteristics below. Do not run PoC code from unknown sources.