GHSA-qr95-4mq5-r3fh is a high-severity (CVSS 7.7) Deserialization of Untrusted Data vulnerability in phpmussel/phpmussel. O3 Security confirms whether GHSA-qr95-4mq5-r3fh is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Phar unserialization vulnerability in phpMussel
Real-World Exposure
phpmussel/phpmussel🐘maikuolan/phpmusselReal-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
Impact
What kind of vulnerability is it? Who is impacted?
Anyone using >= v1.0.0 < v1.6.0.
Patches
Has the problem been patched? What versions should users upgrade to?
Yes. Upgrading to at least >= v1.6.0 (the earliest safe version) will resolve the problem. However, as multiple new major versions have been released since that version, upgrading to the latest available version is recommended, in order to protect against any potential future vulnerabilities, unknown at the time of writing this advisory.
Workarounds
Is there a way for users to fix or remediate the vulnerability without upgrading?
Yes. In the package's configuration, disable archive checking by setting check_archives to false (thus avoiding execution of the affected parts of the codebase entirely).
References
Are there any links users can visit to find out more?
Yes. The vulnerability is documented at SECURITY.md and also at #167.
For more information
If you have any questions or comments about this advisory:
- Comment at the issue linked to this advisory, or..
- Contact the package author.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | phpmussel/phpmussel | ≥ 1.0.0&&< 1.6.0 | 1.6.0 |
| 🐘Packagist | maikuolan/phpmussel | ≥ 1.0.0&&< 1.6.0 | 1.6.0 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for phpmussel/phpmussel. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update phpmussel/phpmussel to 1.6.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-qr95-4mq5-r3fh 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 pinpoints whether GHSA-qr95-4mq5-r3fh is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-qr95-4mq5-r3fh. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-qr95-4mq5-r3fh in your dependencies?
O3 detects GHSA-qr95-4mq5-r3fh across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.