Phpseclib CVE-2026-32935

Risk assessment is complicated by the absence of CVSS vector, EPSS score, and KEV status data, which prevents quantitative prioritization against other vulnerabilities. However, several factors indicate moderate to high real-world risk: (1) The attack is network-observable and does not require authentication or user interaction, (2) Timing-based side-channel attacks are well-understood and tooling exists in the cryptographic community, (3) The library is widely used in PHP applications handling sensitive data, and (4) The presence of patched versions (1.0.27, 2.0.52, 3.0.50) indicates the vendor confirmed the issue as genuine. The attack complexity is moderate—it requires precise timing measurements and multiple requests—but is automatable. Organizations relying on phpseclib for AES-CBC encryption of confidential data (passwords, tokens, PII) should prioritize upgrading. For applications using other cipher modes or encryption libraries, risk is lower.

An attacker observes encrypted authentication tokens or session data transmitted by a PHP web application using vulnerable phpseclib AES-CBC. By sending thousands of specially crafted decryption requests and measuring response times, the attacker can infer which padding configurations are valid, gradually recovering plaintext bytes of the encrypted token. Over the course of minutes to hours depending on network stability, the attacker reconstructs the full plaintext without ever obtaining the encryption key, then reuses the leaked token to impersonate users or escalate privileges. No special tools beyond standard HTTP clients and timing measurement (achievable over the internet via statistical analysis) are required.