Is onelogin/php-saml 4.3 vulnerable?

Composer · 3 releases from 4.3.0 to 4.3.2 · latest onelogin/php-saml is 4.5.0 · checked 18 Nov 2026

No known advisories in the last release

onelogin/php-saml 4.3.2, the last 4.3 release, has no known advisories. 1 advisory affects earlier 4.3.x releases, so update to 4.3.2.

Update within 4.3:composer require onelogin/php-saml:^4.3.2

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

Fixed within 4.3.x, affecting earlier releases

  • 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

Every onelogin/php-saml 4.3.x release

Affected: 4.3.0. 4.3.1 and later are not affected. Latest onelogin/php-saml: 4.5.0.

VersionKnown advisories
onelogin/php-saml 4.3.2None
onelogin/php-saml 4.3.1None
onelogin/php-saml 4.3.0GHSA-5j8p-438x-rgg5

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

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.