The 2026 SAML CVE Wave: Five Checks for Your SAML Stack
Blog post from SSOJet
A series of high- and critical-severity SAML vulnerabilities disclosed in 2026 across authentik, Perl’s Net::SAML2, and the unmaintained npm package passport-saml-encrypted stemmed from a common flaw: applications verified a signed XML element but extracted user identity or authorization data from a different, potentially unsigned element. The issues enabled XML signature wrapping, unsigned assertion injection, acceptance of encrypted but unauthenticated assertions, skipped signature verification when certificates were absent, and failures to enforce expiration, audience, and recipient restrictions; most attacks required only a valid assertion available to an ordinary identity-provider user rather than a stolen signing key. Authentik and Net::SAML2 released patches, while passport-saml-encrypted has no fix and should be removed; the maintained Node SAML packages are unaffected by the 2026 npm CVEs if updated to version 5.1.0 or newer. Recommended defenses include pinning IdP signing certificates, requiring response and assertion signatures, reading identity exclusively from the verified signed subtree, rejecting multiple assertions and duplicate IDs, validating Conditions and replay protections, verifying signatures after decryption, and using one strict XML parser without DTD processing.
| Trend | Post Mentions | Total Month Mentions | Posts | Companies | MoM |
|---|---|---|---|---|---|
| Platform Engineering | 10 | 2,014 | 399 | 102 | +19% |
| Serverless | 1 | 1,384 | 325 | 108 | +12% |
Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.