Which versions of PHP are affected by CVE-2026-32935?

Organizations using phpseclib should be aware of moderate risk from CVE-2026-32935 rated CVSS 5.9. Exploitation could compromise the security of affected deployments.. A patch is available.

How to fix or mitigate CVE-2026-32935?

Within 30 days: Identify affected systems and apply vendor patches as part of regular patch cycle. Monitor vendor channels for patch availability.

PHP CVE-2026-32935

Q: What is the CVSS score of CVE-2026-32935?

CVE-2026-32935 has a CVSS 4.0 base score of 8.2 (High). CVSS vector: CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X. EPSS exploitation probability: 0.0%.

HIGH

Observable Timing Discrepancy (CWE-208)

2026-03-20 security-advisories@github.com

GHSA-94g3-g5v7-q4jg

PHP Oracle Information Disclosure

8.2

CVSS 4.0 · GitHub Advisory

Severity by source

GitHub Advisory PRIMARY

8.2 HIGH

CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Ubuntu

MEDIUM

qualitative

Primary rating from GitHub Advisory.

CVSS VectorGitHub Advisory

CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Attack Vector

Network

Attack Complexity

High

Privileges Required

None

User Interaction

None

Scope

Lifecycle Timeline

Re-analysis Queued

May 08, 2026 - 16:22 vuln.today

cvss_changed

Severity Changed

May 08, 2026 - 16:22 NVD

MEDIUM HIGH

CVSS changed

May 08, 2026 - 16:22 NVD

5.9 (MEDIUM) 8.2 (HIGH)

Patch released

Mar 31, 2026 - 21:13 nvd

Patch available

Analysis Generated

Mar 20, 2026 - 08:37 vuln.today

CVE Published

Mar 20, 2026 - 03:16 nvd

MEDIUM 5.9

DescriptionGitHub Advisory

phpseclib is a PHP secure communications library. Projects using versions 1.0.26 and below, 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.

AnalysisAI

phpseclib versions 1.0.26 and below, 2.0.0 through 2.0.51, and 3.0.0 through 3.0.49 are vulnerable to a padding oracle timing attack when using AES in CBC mode, allowing attackers to decrypt sensitive data through cryptanalysis of response timing differences. This information disclosure vulnerability affects any PHP application using the vulnerable phpseclib library for AES-CBC encryption. Although no CVSS score, EPSS data, or confirmed active exploitation (KEV status) are currently available, the presence of a verified fix and security advisory indicates this is a legitimate cryptographic weakness requiring attention.

Technical ContextAI

phpseclib is a pure PHP cryptographic library providing secure communications functionality including AES encryption. The vulnerability resides in the CBC mode padding validation implementation, which exhibits timing side-channels during decryption—a classic padding oracle weakness classified under CWE-208 (Observable Timing Discrepancy). When decrypting AES-CBC ciphertext, the library's padding verification logic takes measurably different amounts of time depending on whether the padding is valid, leaking information about the plaintext to a network-based attacker who can measure response latency. An attacker can iteratively refine guesses about plaintext bytes by observing timing differences, eventually recovering the original encrypted data without possessing the encryption key.

RemediationAI

Upgrade phpseclib immediately to version 1.0.27, 2.0.52, or 3.0.50 or later depending on your current branch, following the guidance in the GitHub security advisory at https://github.com/phpseclib/phpseclib/security/advisories/GHSA-94g3-g5v7-q4jg. For applications unable to patch immediately, consider switching to authenticated encryption modes (AES-GCM) if possible, or use a higher-level cryptographic library that does not suffer timing side-channels. Additionally, implement network-level defenses such as rate limiting on decryption operations and adding random jitter to response times to reduce timing observability. Conduct an audit of all phpseclib deployments in your infrastructure to identify affected versions and prioritize patches for systems handling sensitive encrypted data.