Is onelogin/php-saml 3.6 vulnerable?
Composer · 2 releases from 3.6.0 to 3.6.1 · latest onelogin/php-saml is 4.5.0 · checked 18 Nov 2026
Yes: 1 known advisory
Yes. onelogin/php-saml 3.6.1, the last 3.6 release, is affected by 1 known security advisory (1 critical). Upgrade to 3.8.1 or later to fix all of them.
composer require onelogin/php-saml:^3.8.1Is your project on an affected onelogin/php-saml?
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.6.1
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 3.6.x release
Affected: 3.6.0 to 3.6.1. Latest onelogin/php-saml: 4.5.0.
| Version | Known advisories |
|---|---|
| onelogin/php-saml 3.6.1 | GHSA-5j8p-438x-rgg5 |
| onelogin/php-saml 3.6.0 | GHSA-5j8p-438x-rgg5 |
Which of your client projects are still on onelogin/php-saml 3.6?
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.