HighGHSA-f2qx-66wf-wvvxCVE-2024-27355

phpseclib guardrails needed on OID length

Published 8 May 2026 · Updated 8 May 2026

Affected packages

phpseclib/phpseclibComposer

Affected: >=2.0.0 <2.0.47
Fixed in: 2.0.47

Update to the fixed version for your release line, for example:composer require phpseclib/phpseclib:^2.0.47

phpseclib/phpseclibComposer

Affected: >=3.0.0 <3.0.36
Fixed in: 3.0.36

Update to the fixed version for your release line, for example:composer require phpseclib/phpseclib:^3.0.36

phpseclib/phpseclibComposer

Affected: >=0.1.1 <1.0.23
Fixed in: 1.0.23

Update to the fixed version for your release line, for example:composer require phpseclib/phpseclib:^1.0.23

Details

Impact

Any application using that loads untrusted ASN1 files (eg. X509 certificates, RSA PKCS8 private or public keys, etc).

Patches

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

Workarounds

No.

Resources

https://github.com/phpseclib/phpseclib/commit/e32531001b4d62c66c3d824ccef54ffad835eb59 https://www.usenix.org/system/files/conference/usenixsecurity25/sec25cycle1-prepub-599-shi-bing.pdf

Is GHSA-f2qx-66wf-wvvx in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected phpseclib/phpseclib, and gives you the command that fixes it.

Scan a project free, no signup Or connect GitHub to scan every repo

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.