SAML PHP Toolkit Vulnerability on xmlseclibs CVE-2025-66475

published 2025-12-09 11mo ago modified 2025-12-09 11mo ago

cvss: —; not scored
cisa kev: Not listed; not in CISA's catalog
epss: —; no score, EPSS covers CVEs only
public exploits: 0; none known

**Summary**

There is a critical vulnerability on xmlseclibs [CVE-2025-66475](https://github.com/robrichards/xmlseclibs/security/advisories/GHSA-c4cc-x928-vjw9), a dependency of php-saml

Update to the following versions of php-saml which forces the use of patched versions of xmlseclibs: - [2.21.1](https://github.com/SAML-Toolkits/php-saml/releases/tag/2.21.1) - [3.8.1](https://github.com/SAML-Toolkits/php-saml/releases/tag/3.8.1) - [4.3.1](https://github.com/SAML-Toolkits/php-saml/releases/tag/4.3.1)

**Impact**

Signature Wrapping Vulnerabilities allows an attacker to impersonate a user.

Patch / fix

fixed in 1 links 3

packagist onelogin/php-saml 2.21.1, 3.8.1, 4.3.1

Is GHSA-5j8p-438x-rgg5 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Affected packages

ecosystem	package	affected	fixed in
packagist	onelogin/php-saml	<2.21.1 >=3.0.0, <3.8.1 >=4.0.0, <4.3.1	2.21.1 3.8.1 4.3.1

Classification

Weakness

CWE-1395 Dependency on Vulnerable Third-Party Component

References

Sources

GitHub Advisory GHSA-5j8p-438x-rgg5

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.