How severe is GHSA-5j8p-438x-rgg5?

No CVSS score has been assigned to GHSA-5j8p-438x-rgg5 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-5j8p-438x-rgg5?

GHSA-5j8p-438x-rgg5 affects the following packages: onelogin/php-saml (Packagist), onelogin/php-saml (Packagist), onelogin/php-saml (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-5j8p-438x-rgg5?

Update onelogin/php-saml to 2.21.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-5j8p-438x-rgg5 is resolved across your whole dependency graph.

How do I detect GHSA-5j8p-438x-rgg5 in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for onelogin/php-saml, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-5j8p-438x-rgg5 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-5j8p-438x-rgg5?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-5j8p-438x-rgg5 can be triaged on real exposure rather than presence alone.

Is GHSA-5j8p-438x-rgg5 actively exploited in the wild?

No public exploit code has been indexed for GHSA-5j8p-438x-rgg5 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-5j8p-438x-rgg5 published, and has it been updated?

GHSA-5j8p-438x-rgg5 was published on December 9, 2025 and was last updated on December 9, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘 Packagist

Not in CISA KEV

GHSA-5j8p-438x-rgg5 — onelogin/php-saml

GHSA-5j8p-438x-rgg5 is a security vulnerability in onelogin/php-saml. A fix is available for onelogin/php-saml — see the affected versions and patch details below.

SAML PHP Toolkit Vulnerability on xmlseclibs CVE-2025-66475

Published

Dec 9, 2025

Updated

Dec 9, 2025

Affected

3 pkgs

Patched

3 / 3

Exploits

None indexed

Exploitation data as of Dec 9, 2025 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

3 pkgs affected

🐘onelogin/php-saml🐘onelogin/php-saml🐘onelogin/php-saml

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.

Description

Summary

There is a critical vulnerability on xmlseclibs CVE-2025-66475, a dependency of php-saml

Update to the following versions of php-saml which forces the use of patched versions of xmlseclibs:

Impact

Signature Wrapping Vulnerabilities allows an attacker to impersonate a user.

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`onelogin/php-saml`	all versions	2.21.1`composer require onelogin/php-saml:^2.21.1`
🐘Packagist	`onelogin/php-saml`	≥ 3.0.0&&< 3.8.1	3.8.1`composer require onelogin/php-saml:^3.8.1`
🐘Packagist	`onelogin/php-saml`	≥ 4.0.0&&< 4.3.1	4.3.1`composer require onelogin/php-saml:^4.3.1`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for onelogin/php-saml, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update onelogin/php-saml to 2.21.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-5j8p-438x-rgg5 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-5j8p-438x-rgg5 can be triaged on real exposure rather than presence alone.

Tailored to GHSA-5j8p-438x-rgg5. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

**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.

O3 Security · Impact-Aware SCA

Is GHSA-5j8p-438x-rgg5 in your dependencies?

O3 Security finds GHSA-5j8p-438x-rgg5 across Packagist dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works