Vulnerability in phpseclib/phpseclib (CVE-2026-32935)
Summary
Vulnerability in phpseclib/phpseclib (CVE-2026-32935). Confidential information can be exposed externally. Mitigation: upgrade to 1.0.27 or later.
Original description
The description as published by the source.
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.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-32935 has been found in phpseclib/phpseclib.
Confidential information can be exposed externally. CVSS score: 5.9/10.
What to do: upgrade phpseclib/phpseclib to 1.0.27 or later.
If unsure, ask your IT team or search "phpseclib/phpseclib CVE-2026-32935" on the vendor's site.
CVE-2026-32935 (phpseclib/phpseclib) — CWE-208 / CVSS v3 5.9
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 1.0.27 — apply immediately
Workaround: Use AES in CTR, CFB or OFB modes
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-208) exists in phpseclib/phpseclib.
Check the vendor advisory for the affected versions of phpseclib/phpseclib.
Severity: Medium (CVSS 5.9/10). Confidential information can be exposed externally.
Update to 1.0.27.
Workaround: Use AES in CTR, CFB or OFB modes
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'phpseclib/phpseclib' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'phpseclib/phpseclib' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
phpseclib/phpseclibを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply temporary workaround mitigate
Use AES in CTR, CFB or OFB modesパッチが適用されるまでの応急処置として、Use AES in CTR, CFB or OFB modes を実施。回避策の副作用 (機能低下) を確認した上で。
-
3Apply patch patch
Upgrade phpseclib/phpseclib to 1.0.27ステージング環境で 1.0.27 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
4Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
Fix status by distribution
Fixed packages published by each distribution for this CVE
- Debian DEBIAN-CVE-2026-32935 php-phpseclib
- Ubuntu UBUNTU-CVE-2026-32935 php-phpseclib Fixed in: 2.0.1-1ubuntu0.1~esm1
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- patch github.com
- web github.com