CVE-2026-44167
HIGHCVE-2026-44167 is a high-severity (CVSS 7.5) Uncontrolled Resource Consumption vulnerability in phpseclib/phpseclib. O3 Security confirms whether CVE-2026-44167 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
phpseclib: CVE-2024-27355 mitigation bypass — OID amplification DoS in ASN1::decodeOID()
Blast Radius
phpseclib/phpseclib🐘phpseclib/phpseclib🐘phpseclib/phpseclibReal-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
phpseclib is a PHP secure communications library. Prior to 1.0.29, 2.0.54, and 3.0.52, anyone loading untrusted ASN1 files (eg. X509 certificates, RSA PKCS8 private or public keys, etc). This is a bypass of CVE-2024-27355. This vulnerability is fixed in 1.0.29, 2.0.54, and 3.0.52.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | phpseclib/phpseclib | ≥ 0.1.1&&< 1.0.29 | 1.0.29 |
| 🐘Packagist | phpseclib/phpseclib | ≥ 2.0.0&&< 2.0.54 | 2.0.54 |
| 🐘Packagist | phpseclib/phpseclib | ≥ 3.0.0&&< 3.0.52 | 3.0.52 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for phpseclib/phpseclib. 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 phpseclib/phpseclib to 1.0.29 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-44167 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 CVE-2026-44167 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 CVE-2026-44167. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2026-44167 in your dependencies?
O3 detects CVE-2026-44167 across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.