Is simplesamlphp/saml2-legacy 4.17 vulnerable?

Composer · 1 release from 4.17.0 to 4.17.0 · latest simplesamlphp/saml2-legacy is 6.3.1 · checked 18 Nov 2026

Yes: 2 known advisories

Yes. simplesamlphp/saml2-legacy 4.17.0, the last 4.17 release, is affected by 2 known security advisories (2 high), including CVE-2026-49289, CVE-2026-49283. Upgrade to 4.19.3 or later to fix all of them.

Upgrade with:composer require simplesamlphp/saml2-legacy:^4.19.3

Is your project on an affected simplesamlphp/saml2-legacy?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Laravel or PHP apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Advisories affecting simplesamlphp/saml2-legacy 4.17.0

  • HighCVE-2026-49289GHSA-5cjr-mxj5-wmrx2 Jul 2026

    SimpleSAMLphp has Possible DoS via XPath Transform

    Affected
    >=4.20.0 <4.20.3 · <4.19.3
    Fixed in
    4.19.3, 4.20.3
  • HighCVE-2026-49283GHSA-6929-8p9f-26jx2 Jul 2026

    SimpleSAMLphp HTTP-Artifact TLS validator confusion allows cross-IdP authentication bypass

    Affected
    >=4.20.0 <4.20.2 · <4.19.3
    Fixed in
    4.19.3, 4.20.2

Which of your client projects are still on simplesamlphp/saml2-legacy 4.17?

NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact simplesamlphp/saml2-legacy version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.

Other simplesamlphp/saml2-legacy versions

Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the Composer registry. Refreshed daily.