← Back
CVE-2026-45074
Vulnerability in symfony/security-http (CVE-2026-45074)
Summary
vulnerability in symfony/security-http (CVE-2026-45074). Risk of unauthorized operations or information disclosure. Exploitable via `Host header`. Mitigation: upgrade to `8.0.12` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-45074** has been found in symfony/security-http.
Attackers can target a specific entry point like `Host header` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: upgrade symfony/security-http to **8.0.12** or later.
If unsure, ask your IT team or search "symfony/security-http CVE-2026-45074" on the vendor's site.
CVE-2026-45074 (symfony/security-http) — CWE-290 /
Attack surface: Host header / `Cas2Handler` / `service` / `Host`
Patched: `8.0.12` — 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-290) exists in symfony/security-http. Attackers reach the vulnerable code path via `Host header` without authentication.
📍 Affected scope
symfony/security-http — . Attack surface: Host header / `Cas2Handler` / `service` / `Host`.
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **8.0.12**.
🛡️ 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 'symfony/security-http' .` 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 'symfony/security-http' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `symfony/security-http` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade symfony/security-http to 8.0.12ステージング環境で 8.0.12 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
composer
symfony/security-http
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"8.0.12"}]}]
composer
symfony/symfony
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"8.0.12"}]}]
Packagist
symfony/security-http
[{"type":"ECOSYSTEM","events":[{"introduced":"8.0.0"},{"fixed":"8.0.12"}]}]
Packagist
symfony/symfony
[{"type":"ECOSYSTEM","events":[{"introduced":"8.0.0"},{"fixed":"8.0.12"}]}]
References
- package https://github.com/symfony/symfony
- web [email protected]
- web [email protected]
- web https://github.com/FriendsOfPHP/security-advisories/blob/master/symfony/security-http/CVE-2026-45074.yaml
- web https://github.com/FriendsOfPHP/security-advisories/blob/master/symfony/symfony/CVE-2026-45074.yaml
- web https://symfony.com/cve-2026-45074
- web https://github.com/advisories/GHSA-j8gj-9rm5-4xhx
- web [email protected]
- web [email protected]