← Back
CVE-2026-24425 high CVSS 8.8

Vulnerability in twig/twig (CVE-2026-24425)

Summary

vulnerability in twig/twig (CVE-2026-24425). Successful exploitation can lead to full system takeover. Exploitable via ``SourcePolicyInterface``. Mitigation: upgrade to `3.26.0` or later.

AI summary snake-internal / snake-material-v2

A vulnerability tracked as **CVE-2026-24425** has been found in twig/twig. Attackers can target a specific entry point like ``SourcePolicyInterface`` over the network to misuse the product. Successful exploitation can lead to full system takeover. CVSS score: 8.8/10. What to do: upgrade twig/twig to **3.26.0** or later. If unsure, ask your IT team or search "twig/twig CVE-2026-24425" on the vendor's site.
CVE-2026-24425 (twig/twig) — CWE-693 / CVSS v3 8.8 Attack vector: remote (network-reachable) / no user interaction Attack surface: `SourcePolicyInterface` / `Closure` / `sort` / `filter` Patched: `3.26.0` — 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
**A vulnerability** (CWE-693) exists in twig/twig. Attackers reach the vulnerable code path via ``SourcePolicyInterface`` without authentication.
📍 Affected scope
twig/twig — . Attack surface: `SourcePolicyInterface` / `Closure` / `sort` / `filter`.
🔥 Severity
Severity: High (CVSS 8.8/10). Successful exploitation can lead to full system takeover
🔧 How to fix
Update to **3.26.0**.
🛡️ 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 'twig/twig' .` 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

  1. 1
    Identify exposure identify
    grep -r 'twig/twig' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `twig/twig` を grep し、稼働しているサービス・バージョンを把握する。

  2. 6
    Apply patch patch
    Upgrade twig/twig to 3.26.0

    ステージング環境で 3.26.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。

  3. 7
    Post-deployment verification verify
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。

Affected packages

composer twig/twig
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.26.0"}]}]
Packagist twig/twig
[{"type":"ECOSYSTEM","events":[{"introduced":"3.9.0"},{"fixed":"3.26.0"}]}]

References

🍪 About cookies

We use cookies to keep you logged in, remember your language, and improve the service.

Details →