Vulnerability in twig/twig (CVE-2026-48805)
Summary
Vulnerability in twig/twig (CVE-2026-48805). Confidential information can be exposed externally. Exploitable via Environment. Mitigation: upgrade to 3.27.0 or later.
Original description
The description as published by the source.
Twig is a template language for PHP. Prior to 3.27.0, deprecated internal wrappers in src/Resources/core.php do not forward the current sandbox state to CoreExtension::checkArrow(), arraySome(), and arrayEvery(), allowing legacy calls such as twig_array_some(), twig_array_every(), and twig_check_arrow_in_sandbox() to bypass sandbox callable restrictions. This issue is fixed in version 3.27.0.
Source: GitHub Security Advisories (Global) 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-48805 has been found in twig/twig.
Attackers can target a specific entry point like Environment over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 9.1/10.
What to do: upgrade twig/twig to 3.27.0 or later.
If unsure, ask your IT team or search "twig/twig CVE-2026-48805" on the vendor's site.
CVE-2026-48805 (twig/twig) — CWE-693 / CVSS v3 9.1
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: Environment / false / Closure / bool
Patched: 3.27.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.
A vulnerability (CWE-693) exists in twig/twig. Attackers reach the vulnerable code path via Environment without authentication.
Check the vendor advisory for the affected versions of twig/twig. Attack surface: Environment / false / Closure / bool.
Severity: Critical (CVSS 9.1/10). Confidential information can be exposed externally.
Update to 3.27.0.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
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
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'twig/twig' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
twig/twigを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade twig/twig to 3.27.0ステージング環境で 3.27.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-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-48805 php-twig
- Ubuntu UBUNTU-CVE-2026-48805 php-twig
References
- advisory github.com
- advisory github.com
- advisory nvd.nist.gov
- package github.com
- patch github.com
- web github.com
- web github.com
- web symfony.com
- web github.com