How severe is CVE-2026-32935?

No CVSS score has been assigned to CVE-2026-32935 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2026-32935?

CVE-2026-32935 affects the following packages: phpseclib/phpseclib (Packagist), phpseclib/phpseclib (Packagist), phpseclib/phpseclib (Packagist). Ecosystems affected: Packagist.

How do I fix CVE-2026-32935?

Update phpseclib/phpseclib to 3.0.50 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-32935 is resolved across your whole dependency graph.

How do I detect CVE-2026-32935 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 CVE-2026-32935 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.

Is CVE-2026-32935 actively exploited in the wild?

No public exploit code has been indexed for CVE-2026-32935 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 CVE-2026-32935?

CVE-2026-32935 has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 34th 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 CVE-2026-32935?

CVE-2026-32935 is classified as CWE-208 (CWE-208). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2026-32935 published, and has it been updated?

CVE-2026-32935 was published on March 20, 2026 and was last updated on October 28, 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

CVE-2026-32935 — phpseclib

Fix: phpseclib/phpseclib@ccc21ae

CVE-2026-32935 is a CWE-208 vulnerability in phpseclib/phpseclib. A fix is available for phpseclib/phpseclib — see the affected versions and patch details below.

phpseclib's AES-CBC unpadding susceptible to padding oracle timing attack

Also known asGHSA-94g3-g5v7-q4jg

Published

Mar 20, 2026

Updated

Oct 28, 2026

Affected

3 pkgs

Patched

3 / 3

Exploits

None indexed

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

Exploitation Status

No confirmed exploitation observed yet

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 CVE-2026-32935.

EPSS Exploitation Probability

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk+0.01%

Lower risk than most CVEs34th percentile — riskier than 34% of all scored CVEsHighest risk

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

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

phpseclib is a PHP secure communications library. Projects using versions 0.1.1 through 1.0.26, 2.0.0 through 2.0.51, and 3.0.0 through 3.0.49 are vulnerable to a to padding oracle timing attack when using AES in CBC mode. This issue has been fixed in versions 1.0.27, 2.0.52 and 3.0.50.

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`phpseclib/phpseclib`	≥ 3.0.0&&< 3.0.50	3.0.50`composer require phpseclib/phpseclib:^3.0.50`
🐘Packagist	`phpseclib/phpseclib`	≥ 2.0.0&&< 2.0.52	2.0.52`composer require phpseclib/phpseclib:^2.0.52`
🐘Packagist	`phpseclib/phpseclib`	≥ 0.1.1&&< 1.0.27	1.0.27`composer require phpseclib/phpseclib:^1.0.27`

Affected Products

1 product · 3 configurations

Application

phpseclibphpseclib

≥ 3.0.0 && < 3.0.50

range

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 3.0.50 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-32935 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.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2026-32935 in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works