How severe is GHSA-3qpq-r242-jqj7?

GHSA-3qpq-r242-jqj7 has a CVSS score of 7.5/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-3qpq-r242-jqj7?

GHSA-3qpq-r242-jqj7 affects the following packages: phpseclib/phpseclib (Packagist), phpseclib/phpseclib (Packagist), phpseclib/phpseclib (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-3qpq-r242-jqj7?

Update phpseclib/phpseclib to 1.0.29 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-3qpq-r242-jqj7 is resolved across your whole dependency graph.

How do I detect GHSA-3qpq-r242-jqj7 in my Packagist dependencies?

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

How do I mitigate GHSA-3qpq-r242-jqj7 if there is no patch (or I can't update yet)?

Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Is GHSA-3qpq-r242-jqj7 actively exploited in the wild?

No public exploit code has been indexed for GHSA-3qpq-r242-jqj7 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.

What is the EPSS score for GHSA-3qpq-r242-jqj7?

GHSA-3qpq-r242-jqj7 has an EPSS (Exploit Prediction Scoring System) score of 0.2%, placing it in the 10th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-3qpq-r242-jqj7?

GHSA-3qpq-r242-jqj7 is classified as Uncontrolled Resource Consumption (CWE-400). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-3qpq-r242-jqj7 published, and has it been updated?

GHSA-3qpq-r242-jqj7 was published on May 5, 2026 and was last updated on September 10, 2026. 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

HIGH severity

phpseclib has a CVE-2024-27355 mitigation bypass — OID amplification DoS in ASN1::decodeOID()GHSA-3qpq-r242-jqj7

HIGHFix: phpseclib/phpseclib@d53d202

GHSA-3qpq-r242-jqj7 is a high-severity (CVSS 7.5) Uncontrolled Resource Consumption vulnerability in phpseclib/phpseclib. A fix is available for phpseclib/phpseclib — see the affected versions and patch details below.

Also known asCVE-2026-44167

Published

May 5, 2026

Updated

Sep 10, 2026

Affected

3 pkgs

Patched

3 / 3

Exploits

None indexed

Exploitation data as of Nov 5, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-3qpq-r242-jqj7.

EPSS Exploitation Probability

via FIRST.org ↗

0.2%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs10th percentile — riskier than 10% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

3 pkgs affected

🐘phpseclib/phpseclib🐘phpseclib/phpseclib🐘phpseclib/phpseclib

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

Impact

Anyone loading untrusted ASN1 files (eg. X509 certificates, RSA PKCS8 private or public keys, etc)

Patches

https://github.com/phpseclib/phpseclib/commit/d53d2021bcb9f6a04d5d44ec99e6bbef219a71bc

Workarounds

No.

References

https://github.com/phpseclib/phpseclib/commit/d53d2021bcb9f6a04d5d44ec99e6bbef219a71bc

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`phpseclib/phpseclib`	≥ 0.1.1&&< 1.0.29	1.0.29`composer require phpseclib/phpseclib:^1.0.29`
🐘Packagist	`phpseclib/phpseclib`	≥ 2.0.0&&< 2.0.54	2.0.54`composer require phpseclib/phpseclib:^2.0.54`
🐘Packagist	`phpseclib/phpseclib`	≥ 3.0.0&&< 3.0.52	3.0.52`composer require phpseclib/phpseclib:^3.0.52`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for phpseclib/phpseclib, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update phpseclib/phpseclib to 1.0.29 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-3qpq-r242-jqj7 is resolved across your whole dependency graph.
Workarounds
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Frequently Asked Questions

### Impact Anyone loading untrusted ASN1 files (eg. X509 certificates, RSA PKCS8 private or public keys, etc) ### Patches https://github.com/phpseclib/phpseclib/commit/d53d2021bcb9f6a04d5d44ec99e6bbef219a71bc ### Workarounds No. ### References https://github.com/phpseclib/phpseclib/commit/d53d2021bcb9f6a04d5d44ec99e6bbef219a71bc