← Back
CVE-2026-7261
critical
CVSS 9.8
Use-After-Free in libphp (CVE-2026-7261)
Summary
vulnerability in libphp (CVE-2026-7261). Successful exploitation can lead to full system takeover. Mitigation: upgrade to `8.2.31, 8.3.31, 8.4.21, 8.5.6` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-7261** has been found in libphp.
Successful exploitation can lead to full system takeover. CVSS score: 9.8/10.
What to do: upgrade libphp to **8.2.31, 8.3.31, 8.4.21, 8.5.6** or later.
If unsure, ask your IT team or search "libphp CVE-2026-7261" on the vendor's site.
CVE-2026-7261 (libphp) — CWE-416 / CVSS v3 9.8
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: `8.2.31, 8.3.31, 8.4.21, 8.5.6` — apply immediately
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.
❓ What is the problem
**use-after-free** (CWE-416) exists in libphp.
📍 Affected scope
libphp — .
🔥 Severity
Severity: Critical (CVSS 9.8/10). Successful exploitation can lead to full system takeover
🔧 How to fix
Update to **8.2.31, 8.3.31, 8.4.21, 8.5.6**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'libphp' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'libphp' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `libphp` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade libphp to 8.2.31, 8.3.31, 8.4.21, 8.5.6ステージング環境で 8.2.31, 8.3.31, 8.4.21, 8.5.6 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
Bitnami
libphp
[{"type":"SEMVER","events":[{"introduced":"8.2.0"},{"fixed":"8.2.31"},{"introduced":"8.3.0"},{"fixed":"8.3.31"},{"introduced":"8.4.0"},{"fixed":"8.4.21"},{"introduced":"8.5.0"},{"fixed":"8.5.6"}]}]
Bitnami
php
[{"type":"SEMVER","events":[{"introduced":"8.2.0"},{"fixed":"8.2.31"},{"introduced":"8.3.0"},{"fixed":"8.3.31"},{"introduced":"8.4.0"},{"fixed":"8.4.21"},{"introduced":"8.5.0"},{"fixed":"8.5.6"}]}]
Bitnami
php-min
[{"type":"SEMVER","events":[{"introduced":"8.2.0"},{"fixed":"8.2.31"},{"introduced":"8.3.0"},{"fixed":"8.3.31"},{"introduced":"8.4.0"},{"fixed":"8.4.21"},{"introduced":"8.5.0"},{"fixed":"8.5.6"}]}]