← Back
CVE-2026-41570
high
CVSS 7.8
Vulnerability in phpunit/phpunit (CVE-2026-41570)
Summary
vulnerability in phpunit/phpunit (CVE-2026-41570). Successful exploitation can lead to full system takeover. Exploitable via ``auto_prepend_file``. Mitigation: upgrade to `13.1.6` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-41570** has been found in phpunit/phpunit.
Attackers can target a specific entry point like ``auto_prepend_file`` over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 7.8/10.
What to do: upgrade phpunit/phpunit to **13.1.6** or later.
If unsure, ask your IT team or search "phpunit/phpunit CVE-2026-41570" on the vendor's site.
CVE-2026-41570 (phpunit/phpunit) — CWE-88 / CVSS v3 7.8
Attack vector: local / no user interaction
Attack surface: `auto_prepend_file` / `extension` / `disable_functions` / `open_basedir`
Patched: `13.1.6` — apply immediately
Workaround: - Audit INI values: Ensure no `<ini value="…">` entry in `phpunit.
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
**A vulnerability** (CWE-88) exists in phpunit/phpunit. Attackers reach the vulnerable code path via ``auto_prepend_file`` without authentication.
📍 Affected scope
phpunit/phpunit — . Attack surface: `auto_prepend_file` / `extension` / `disable_functions` / `open_basedir`.
🔥 Severity
Severity: High (CVSS 7.8/10). Successful exploitation can lead to full system takeover
🔧 How to fix
Update to **13.1.6**.
🛡️ Workaround
Workaround: - Audit INI values: Ensure no `<ini value="…">` entry in `phpunit.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'phpunit/phpunit' .` 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 'phpunit/phpunit' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `phpunit/phpunit` を grep し、稼働しているサービス・バージョンを把握する。
-
5Apply temporary workaround mitigate
- Audit INI values: Ensure no `<ini value="…">` entry in `phpunit.パッチが適用されるまでの応急処置として、- Audit INI values: Ensure no `<ini value="…">` entry in `phpunit. を実施。回避策の副作用 (機能低下) を確認した上で。
-
6Apply patch patch
Upgrade phpunit/phpunit to 13.1.6ステージング環境で 13.1.6 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
composer
phpunit/phpunit
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"13.1.6"}]}]
Packagist
phpunit/phpunit
[{"type":"ECOSYSTEM","events":[{"introduced":"13.1.5"},{"fixed":"13.1.6"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2026-41570
- package https://github.com/sebastianbergmann/phpunit
- web https://github.com/sebastianbergmann/phpunit/pull/6592
- web https://github.com/sebastianbergmann/phpunit/security/advisories/GHSA-qrr6-mg7r-m243
- web https://github.com/FriendsOfPHP/security-advisories/blob/master/phpunit/phpunit/CVE-2026-41570.yaml
- web https://github.com/advisories/GHSA-qrr6-mg7r-m243