VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

saml2-js: vulnerability history, versions and safety

saml2-js is a package in the npm ecosystem. Vulert records 2 vulnerabilities for it across 48 releases, from Jul 2019 to Sep 2020. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
2 vulnerabilities recorded M2
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all saml2-js vulnerabilities

Vulert verdict on saml2-js 4.0.4 i

Updated on 22 Oct 2026

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

Package health score 68/100
  • Security Minor issues
  • Maintenance Maintaining
  • Popularity Niche
  • Community Quiet

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

  • Current release 4.0.4 — unaffected i
  • Vulnerabilities on record 2 over 1 year · 0 in the last year i
  • Latest disclosure 03 Sep 2020 i
  • Highest CVSS 7.7 i
  • With no published fix 0 i
  • Depended on by 76 packages i
  • Stars 362 i
  • OpenSSF scorecard 3/10 i
  • Last release 15 months ago i
  • Licence Apache-2.0 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 saml2-js, 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
4.0.4 07 Jul 2025 none Apache-2.0 — Details →
4.0.3 18 Mar 2025 none Apache-2.0 — Details →
4.0.2 10 May 2023 none Apache-2.0 — Details →
4.0.1 08 Nov 2022 none Apache-2.0 — Details →
4.0.0 15 Oct 2022 none Apache-2.0 — Details →
3.1.0 15 Oct 2022 none Apache-2.0 — Details →
3.0.1 08 Feb 2021 none Apache-2.0 — Details →
3.0.0 04 Feb 2021 none Apache-2.0 — Details →
2.1.0 04 Feb 2021 none Apache-2.0 — Details →
2.0.9 03 Feb 2021 none Apache-2.0 — Details →
2.0.8 03 Feb 2021 none Apache-2.0 — Details →
2.0.7 25 Jan 2021 none Apache-2.0 — Details →
2.0.6 23 Oct 2020 none Apache-2.0 — Details →
2.0.5 16 Oct 2019 none Apache-2.0 — Details →
2.0.3 16 May 2018 M1 Apache-2.0 Yes Details →
2.0.2 23 Feb 2018 M1 Apache-2.0 Yes Details →
1.12.4 23 Feb 2018 M1 Apache-2.0 Yes Details →
2.0.1 30 Nov 2017 M1 Apache-2.0 Yes Details →
2.0.0 03 Nov 2017 M1 Apache-2.0 Yes Details →
1.12.3 03 Nov 2017 M2 Apache-2.0 Yes Details →
1.12.2 08 Aug 2017 M2 Apache-2.0 Yes Details →
1.12.1 07 Aug 2017 M2 Apache-2.0 Yes Details →
1.11.1 11 May 2017 M2 Apache-2.0 Yes Details →
1.11.0 21 Dec 2016 M2 Apache-2.0 Yes Details →
1.10.0 13 Sep 2016 M2 Apache-2.0 Yes Details →
1.9.0 12 Sep 2016 M2 Apache-2.0 Yes Details →
1.8.1 30 Aug 2016 M2 Apache-2.0 Yes Details →
1.8.0 04 Aug 2016 M2 Apache-2.0 Yes Details →
1.7.0 24 Jun 2016 M2 Apache-2.0 Yes Details →
1.6.0 03 Jun 2016 M2 Apache-2.0 Yes Details →
1.5.1 06 Apr 2016 M2 Apache-2.0 Yes Details →
1.5.0 06 Apr 2016 M2 Apache-2.0 Yes Details →
1.4.4 09 Mar 2016 M2 Apache-2.0 Yes Details →
1.4.3 25 Feb 2016 M2 Apache-2.0 Yes Details →
1.4.2 12 Feb 2016 M2 Apache-2.0 Yes Details →
1.4.1 12 Jan 2016 M2 Apache-2.0 Yes Details →
1.4.0 12 Jan 2016 M2 Apache-2.0 Yes Details →
1.3.0 18 Dec 2015 M2 Apache-2.0 Yes Details →
1.2.0 05 Nov 2015 M2 Apache-2.0 Yes Details →
1.1.0 05 Nov 2015 M2 Apache-2.0 Yes Details →
1.0.3 09 Oct 2015 M2 Apache-2.0 Yes Details →
1.0.2 29 Jul 2015 M2 Apache-2.0 Yes Details →
1.0.1 15 May 2015 M2 Apache-2.0 Yes Details →
1.0.0 15 May 2015 M2 Apache-2.0 Yes Details →
0.8.1 23 Apr 2015 M2 Apache-2.0 Yes Details →
0.8.0 20 Apr 2015 M2 Apache-2.0 Yes Details →
0.7.0 17 Apr 2015 M2 Apache-2.0 Yes Details →
0.6.2 17 Apr 2015 M2 Apache-2.0 Yes Details →
0.6.1 17 Apr 2015 M2 Apache-2.0 Yes Details →
0.6.0 10 Mar 2015 M2 Apache-2.0 Yes Details →
0.5.1 09 Mar 2015 M2 Apache-2.0 Yes Details →
0.5.0 22 Jan 2015 M2 Apache-2.0 Yes Details →
0.4.0 05 Dec 2014 M2 Apache-2.0 Yes Details →
0.3.0 16 Oct 2014 M2 Apache-2.0 Yes Details →
0.2.5 26 Aug 2014 M2 Apache-2.0 Yes Details →
0.2.7 07 Aug 2014 M2 Apache-2.0 Yes Details →
0.2.4 20 Jun 2014 M2 Apache-2.0 Yes Details →
0.2.3 01 May 2014 M2 Apache-2.0 Yes Details →
0.2.2 23 Apr 2014 M2 Apache-2.0 Yes Details →
0.2.1 22 Apr 2014 M2 Apache-2.0 Yes Details →
0.2.0 09 Apr 2014 M2 Apache-2.0 Yes Details →
0.1.1 04 Apr 2014 M2 Apache-2.0 Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2019 1
  • 2020 1

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

03 Vulnerabilities

Recorded vulnerabilities for saml2-js

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2017-11429: Authentication bypass via incorrect XML canonicalization and DOM traversal in saml2-js 7.7 medium 1.12.4 05 Jul 2019
Authentication Bypass in saml2-js 6.8 medium 2.0.5 03 Sep 2020

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

Updated: 22/Oct/2026 · Vulnerabilities in our DB: 524173

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 saml2-js

Is saml2-js safe to use?

Vulert records 2 vulnerabilities for saml2-js in npm: 0 critical, 0 high, 2 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 saml2-js's Vulert package health score?

Vulert scores saml2-js 68/100, which reads as usable, but worth attention. 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 saml2-js affected?

No. 4.0.4, 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.

Which version of saml2-js should I use?

4.0.4 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does saml2-js have?

2 vulnerabilities are recorded for saml2-js in the npm ecosystem: 0 critical, 0 high, 2 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 saml2-js vulnerabilities disclosed?

0 vulnerabilities were recorded for saml2-js in the last 12 months, and the oldest entry in this database dates to 05 Jul 2019. 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 saml2-js 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 saml2-js for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the saml2-js version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.