VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

samlify: vulnerability history, versions and safety

samlify is a package in the npm ecosystem. Vulert records 3 vulnerabilities for it across 70 releases, from Jan 2018 to May 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
3 vulnerabilities recorded C1 H2
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
1 in the last 12 months

Most recent disclosure 21 May 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all samlify vulnerabilities

Vulert verdict on samlify 2.15.1 i

Updated on 23 Oct 2026

Good news: 2.15.1, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 3.

Package health score 74/100
  • Security Some issues to review
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Quiet

What to do: Stay on 2.15.1 or newer. This can change: a vulnerability disclosed tomorrow can affect 2.15.1 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 2.15.1 — unaffected i
  • Vulnerabilities on record 3 over 8 years · 1 in the last year i
  • Latest disclosure 21 May 2026 i
  • Highest CVSS 9.9 i
  • With no published fix 0 i
  • Depended on by 120 packages i
  • Stars 662 i
  • OpenSSF scorecard 3/10 i
  • Last release this month i
  • Licence MIT i

Version list, release dates, licence and dependants published by the npm registry, refreshed 23 Oct 2026. 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 Versions

Which versions are affected

Every version Vulert tracks for samlify, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
2.15.1 21 Oct 2026 none MIT — Details →
2.15.0 20 Oct 2026 none MIT — Details →
2.14.0 17 Oct 2026 none MIT — Details →
2.13.1 18 May 2026 none MIT — Details →
2.13.0 14 May 2026 none MIT — Details →
2.12.0 31 Mar 2026 H1 MIT Yes Details →
2.11.0 09 Mar 2026 H1 MIT Yes Details →
2.10.2 28 Nov 2025 H1 MIT Yes Details →
2.10.1 06 Jul 2025 H1 MIT Yes Details →
2.10.0 06 May 2025 H1 MIT Yes Details →
2.9.1 24 Mar 2025 C1 H1 MIT Yes Details →
2.9.0 15 Mar 2025 C1 H1 MIT Yes Details →
2.8.11 02 Mar 2024 C1 H1 MIT Yes Details →
2.8.10 26 Feb 2023 C1 H1 MIT Yes Details →
2.8.9 14 Feb 2023 C1 H1 MIT Yes Details →
2.8.8 20 Jan 2023 C1 H1 MIT Yes Details →
2.8.7 06 Nov 2022 C1 H1 MIT Yes Details →
2.8.6 13 Oct 2022 C1 H1 MIT Yes Details →
2.8.5 24 May 2022 C1 H1 MIT Yes Details →
2.8.4 05 Apr 2022 C1 H1 MIT Yes Details →
2.8.3 11 Feb 2022 C1 H1 MIT Yes Details →
2.8.2 19 Sep 2021 C1 H1 MIT Yes Details →
2.8.1 06 Sep 2021 C1 H1 MIT Yes Details →
2.8.0 05 Sep 2021 C1 H1 MIT Yes Details →
2.8.0-rc1 12 Jul 2021 C1 H1 MIT Yes Details →
2.7.7 10 Jun 2021 C1 H1 MIT Yes Details →
2.7.6 30 Oct 2020 C1 H1 MIT Yes Details →
2.7.5 03 Sep 2020 C1 H1 MIT Yes Details →
2.7.4 15 May 2020 C1 H1 MIT Yes Details →
2.7.3 14 Apr 2020 C1 H1 MIT Yes Details →
2.7.2 04 Apr 2020 C1 H1 MIT Yes Details →
2.7.1 30 Jan 2020 C1 H1 MIT Yes Details →
2.7.0 28 Jan 2020 C1 H1 MIT Yes Details →
2.6.3 18 Jan 2020 C1 H1 MIT Yes Details →
2.6.2 12 Nov 2019 C1 H1 MIT Yes Details →
2.6.1 10 Aug 2019 C1 H1 MIT Yes Details →
2.6.0 07 Jul 2019 C1 H1 MIT Yes Details →
2.6.0-rc2 25 Jun 2019 C1 H1 MIT Yes Details →
2.5.1 25 Jun 2019 C1 H1 MIT Yes Details →
2.6.0-rc1 23 Jun 2019 C1 H1 MIT Yes Details →
2.5.0 08 Apr 2019 C1 H1 MIT Yes Details →
2.5.0-rc4 14 Mar 2019 C1 H1 MIT Yes Details →
2.5.0-rc3 13 Mar 2019 C1 H1 MIT Yes Details →
2.5.0-rc2 22 Feb 2019 C1 H1 MIT Yes Details →
2.5.0-rc1 12 Jan 2019 C1 H1 MIT Yes Details →
2.4.2 29 Dec 2018 C1 H1 MIT Yes Details →
2.4.1 13 Nov 2018 C1 H1 MIT Yes Details →
2.4.0 20 Oct 2018 C1 H1 MIT Yes Details →
2.4.0-rc6 17 Oct 2018 C1 H1 MIT Yes Details →
2.4.0-rc5 06 Oct 2018 C1 H1 MIT Yes Details →
2.4.0-rc4 26 Sep 2018 C1 H2 MIT Yes Details →
2.4.0-rc3 26 Sep 2018 C1 H2 MIT Yes Details →
2.4.0-rc2 22 Aug 2018 C1 H2 MIT Yes Details →
2.4.0-rc1 25 Jul 2018 C1 H2 MIT Yes Details →
2.3.8 10 Jul 2018 C1 H2 MIT Yes Details →
2.3.7 21 Mar 2018 C1 H2 MIT Yes Details →
2.3.6 10 Nov 2017 C1 H2 MIT Yes Details →
2.3.5 04 Nov 2017 C1 H2 MIT Yes Details →
2.3.4 20 Oct 2017 C1 H2 MIT Yes Details →
2.3.3 13 Oct 2017 C1 H2 MIT Yes Details →
2.3.2 04 Oct 2017 C1 H2 MIT Yes Details →
2.3.1 03 Oct 2017 C1 H2 MIT Yes Details →
2.3.0 22 Sep 2017 C1 H2 MIT Yes Details →
2.2.0 11 Aug 2017 C1 H2 MIT Yes Details →
2.1.1 25 Jul 2017 C1 H2 MIT Yes Details →
2.1.0 19 Jul 2017 C1 H2 MIT Yes Details →
2.0.4 07 Jul 2017 C1 H2 MIT Yes Details →
2.0.3 04 Jul 2017 C1 H2 MIT Yes Details →
2.0.2 30 Jun 2017 C1 H2 MIT Yes Details →
2.0.1 29 Jun 2017 C1 H2 MIT Yes Details →
2.0.0 25 Jun 2017 C1 H2 MIT Yes Details →
2.0.1-rc.3 20 Jun 2017 C1 H2 MIT Yes Details →
2.0.0-rc.3 20 Jun 2017 C1 H2 MIT Yes Details →
2.0.0-rc.2 16 Jun 2017 C1 H2 MIT Yes Details →
2.0.0-rc.1 06 Jun 2017 C1 H2 MIT Yes Details →

All 75 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2018 1
  • 2025 1
  • 2026 1

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 1 of the 3 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for samlify

The 3 most severe of 3 vulnerabilities recorded for this package

Search all 3 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

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About samlify

Is samlify safe to use?

Vulert records 3 vulnerabilities for samlify in npm: 1 critical, 2 high, 0 medium and 0 low. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is samlify's Vulert package health score?

Vulert scores samlify 74/100, which reads as in good shape. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).

Is the latest version of samlify affected?

No. 2.15.1, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

How many vulnerabilities does samlify have?

3 vulnerabilities are recorded for samlify in the npm ecosystem: 1 critical, 2 high, 0 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new samlify vulnerabilities disclosed?

1 vulnerability was recorded for samlify in the last 12 months, and the oldest entry in this database dates to 04 Jan 2018. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of samlify are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

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.