Is onelogin/php-saml 3.7 vulnerable?

Composer · 1 release from 3.7.0 to 3.7.0 · latest onelogin/php-saml is 4.5.0 · checked 18 Nov 2026

Yes: 1 known advisory

Yes. onelogin/php-saml 3.7.0, the last 3.7 release, is affected by 1 known security advisory (1 critical). Upgrade to 3.8.1 or later to fix all of them.

Upgrade with:composer require onelogin/php-saml:^3.8.1

Is your project on an affected onelogin/php-saml?

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 onelogin/php-saml 3.7.0

  • CriticalGHSA-5j8p-438x-rgg59 Dec 2025

    SAML PHP Toolkit Vulnerability on xmlseclibs CVE-2025-66475

    Affected
    <2.21.1 · >=3.0.0 <3.8.1 · >=4.0.0 <4.3.1
    Fixed in
    2.21.1, 3.8.1, 4.3.1

Which of your client projects are still on onelogin/php-saml 3.7?

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

Other onelogin/php-saml 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.