Vulnerability Database · npm · samlify · Version
samlify 2.3.1
2.3.1 is affected by 3 vulnerabilities.
The vulnerabilities that cover this exact version are listed below with the fixed version to move to.
Critical 1 High 2 Medium 0 Low 0 Unrated 0
-
Released 03 Oct 2017
Licence MIT
Also known from other sources 3
Newer releases 75
Database updated 23/Oct/2026
Release and licence data published by the npm registry. Licence information is not legal advice.
Concerned about your application's security?
Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.
01 Vulnerabilities affecting this version
samlify 2.3.1 vulnerabilities
3 vulnerabilities cover samlify 2.3.1. Open the full list in the database.
| Vulnerability | Severity | Fixed version | Disclosed |
|---|---|---|---|
| CVE-2025-47949: samlify SAML Signature Wrapping Attack Vulnerability | 9.9 critical | 2.10.0 | 19 May 2025 |
| CVE-2026-46490: samlify XML Injection Vulnerability Leading to Privilege Escalation | 8.7 high | 2.13.0 | 21 May 2026 |
| CVE-2017-1000452: Authentication Bypass in samlify | 7.5 high | 2.4.0-rc5 | 04 Jan 2018 |
Looking for another version, or everything Vulert holds for samlify?
Questions
About samlify 2.3.1
Is samlify 2.3.1 vulnerable?
Yes. 3 vulnerabilities in the Vulert database cover samlify 2.3.1: 1 critical, 2 high, 0 medium and 0 low. Each entry above names the fixed version to move to.
Is 2.3.1 the latest release of samlify?
No. 2.3.1 was published 03 Oct 2017, and newer releases exist. Newer is not automatically safer — the version table on the package page shows what each release carries.
How do I monitor samlify for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the samlify version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.