Vulnerability Database · Packagist · Package report

simplesamlphp/saml2: vulnerability history, versions and safety

simplesamlphp/saml2 is a package in the Packagist ecosystem. Vulert records 8 vulnerabilities for it across 120 releases, from May 2022 to Jul 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
8 vulnerabilities recorded C1 H6 M1
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
2 in the last 12 months

Most recent disclosure 02 Jul 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

Vulert verdict on simplesamlphp/saml2 i

Updated on 23 Oct 2026

Every vulnerability Vulert records for this package has a fix, and the newest was recorded 02 Jul 2026. Apply the fixes listed below and you are clear.

Long-term outlook: usable, with an upgrade 8 vulnerabilities on record across 4 years, 2 in the last year.

What to do: Move the affected dependencies to the fixed versions listed below, then keep the package monitored so the next vulnerability reaches you. Fix it, then keep watch: Vulert alerts you when a new vulnerability affects the version you run. Monitor it with Vulert →

  • Vulnerabilities on record 8 over 4 years · 2 in the last year i
  • Latest disclosure 02 Jul 2026 i
  • Highest CVSS 9.1 i
  • With no published fix 0 i

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 holds for simplesamlphp/saml2, newest first, with the vulnerabilities that name it. A version with a count of zero has no recorded vulnerabilities; open a version to see the vulnerabilities it is exposed to.

i
Version Vulert vulnerabilities Fix published Details
4.6.9 H2 M1 Yes Details →
v6.2.0 H1 Yes Details →
v6.1.6 H1 Yes Details →
v6.1.5 H1 Yes Details →
v6.1.4 H1 Yes Details →
v6.1.3 H1 Yes Details →
v6.1.2 H1 Yes Details →
v6.1.1 H1 Yes Details →
v6.1.0 H1 Yes Details →
v6.0.1 H1 Yes Details →
v6.0.0 H1 Yes Details →
v4.20.2 H1 Yes Details →
v4.20.1 H1 Yes Details →
v4.20.0 H1 Yes Details →
v4.19.2 H1 Yes Details →
v4.19.1 H1 Yes Details →
v4.19.0 H1 Yes Details →
v4.18.1 H1 Yes Details →
v4.18.0 H1 Yes Details →
v4.17.0 H1 Yes Details →
v4.16.14 H2 Yes Details →
v4.6.16 H2 Yes Details →
v4.6.15 H2 Yes Details →
v4.6.14 H2 Yes Details →
v4.6.13 H2 M1 Yes Details →
v4.6.12 H2 M1 Yes Details →
v4.6.11 H2 M1 Yes Details →
v4.6.10 H2 M1 Yes Details →
v4.6.8 H2 M1 Yes Details →
v4.6.7 H2 M1 Yes Details →
v4.6.6 H2 M1 Yes Details →
v4.6.5 H2 M1 Yes Details →
v4.6.4 H2 M1 Yes Details →
v4.6.3 H2 M1 Yes Details →
v4.6.2 H2 M1 Yes Details →
v4.6.1 H2 M1 Yes Details →
v4.6.0 H2 M1 Yes Details →
v4.5.1 H2 M1 Yes Details →
v4.5.0 H2 M1 Yes Details →
v4.4.1 H2 M1 Yes Details →
v4.4.0 H2 M1 Yes Details →
v4.3.1 H2 M1 Yes Details →
v4.3.0 H2 M1 Yes Details →
v4.2.8 H2 M1 Yes Details →
v4.2.7 H2 M1 Yes Details →
v4.2.6 H2 M1 Yes Details →
v4.2.5 H2 M1 Yes Details →
v4.2.4 H2 M1 Yes Details →
v4.2.3 H2 M1 Yes Details →
v4.2.2 H2 M1 Yes Details →
v4.2.1 H2 M1 Yes Details →
v4.2.0 H2 M1 Yes Details →
v4.1.12 H2 M1 Yes Details →
v4.1.11 H2 M1 Yes Details →
v4.1.10 H2 M1 Yes Details →
v4.1.9 H2 M1 Yes Details →
v4.1.8 H2 M1 Yes Details →
v4.1.7 H2 M1 Yes Details →
v4.1.6 H2 M1 Yes Details →
v4.1.5 H2 M1 Yes Details →
v4.1.4 H2 M1 Yes Details →
v4.1.3 H2 M1 Yes Details →
v4.1.2 H2 M1 Yes Details →
v4.1.1 H2 M1 Yes Details →
v4.1.0 H2 M1 Yes Details →
v4.0.3 H2 M1 Yes Details →
v4.0.2 H2 M1 Yes Details →
v4.0.1 H2 M1 Yes Details →
v4.0.0 H2 M1 Yes Details →
v3.4.5 H2 M1 Yes Details →
v3.4.4 H2 M1 Yes Details →
v3.4.3 H2 M1 Yes Details →
v3.4.2 H2 M1 Yes Details →
v3.4.1 H2 M1 Yes Details →
v3.4.0 H2 M1 Yes Details →
v3.3.11 H2 M1 Yes Details →
v3.3.10 H2 M1 Yes Details →
v3.3.9 H2 M1 Yes Details →
v3.3.8 H2 M1 Yes Details →
v3.3.7 H2 M1 Yes Details →
v3.3.6 H2 M1 Yes Details →
v3.3.5 H2 M1 Yes Details →
v3.3.4 H2 M1 Yes Details →
v3.3.3 H2 M1 Yes Details →
v3.3.2 H2 M1 Yes Details →
v3.3.1 H2 M1 Yes Details →
v3.3.0 H2 M1 Yes Details →
v3.2.6 H2 M1 Yes Details →
v3.2.5 H2 M1 Yes Details →
v3.2.4 H2 M1 Yes Details →
v3.2.3 H2 M1 Yes Details →
v3.2.2 H2 M1 Yes Details →
v3.2.1 H2 M1 Yes Details →
v3.2 H2 M1 Yes Details →
v3.1.6 H2 M1 Yes Details →
v3.1.5 H2 M1 Yes Details →
v3.1.4 H2 M1 Yes Details →
v3.1.3 H2 M1 Yes Details →
v3.1.2 H2 M1 Yes Details →
v3.1.1 H2 M1 Yes Details →
v3.1.0 H2 M1 Yes Details →
v3.0.3 H2 M1 Yes Details →
v3.0.2 H2 M1 Yes Details →
v3.0.1 H2 M1 Yes Details →
v3.0.0 H2 M1 Yes Details →
v2.3.9 H2 M1 Yes Details →
v2.3.8 H2 M1 Yes Details →
v2.3.7 H2 M1 Yes Details →
v2.3.6 H2 M1 Yes Details →
v2.3.5 H2 M1 Yes Details →
v2.3.4 H2 M1 Yes Details →
v2.3.3 H2 M1 Yes Details →
v2.3.2 H2 M1 Yes Details →
v2.3.1 H2 M1 Yes Details →
v2.3 H2 M1 Yes Details →
v2.2 H2 M1 Yes Details →
v2.1 H2 M1 Yes Details →
v2.0.1 H2 M1 Yes Details →
v2.0.0 H2 M1 Yes Details →
v1.10.6 H2 M1 Yes Details →

Newest 120 of 165 versions on record. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2022 4
  • 2024 1
  • 2025 1
  • 2026 2

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

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 simplesamlphp/saml2

Is simplesamlphp/saml2 safe to use?

Vulert records 8 vulnerabilities for simplesamlphp/saml2 in Packagist: 1 critical, 6 high, 1 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.

How many vulnerabilities does simplesamlphp/saml2 have?

8 vulnerabilities are recorded for simplesamlphp/saml2 in the Packagist ecosystem: 1 critical, 6 high, 1 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 simplesamlphp/saml2 vulnerabilities disclosed?

2 vulnerabilities were recorded for simplesamlphp/saml2 in the last 12 months, and the oldest entry in this database dates to 13 May 2022. 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 simplesamlphp/saml2 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 simplesamlphp/saml2 for upcoming vulnerabilities?

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