Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-48489 high CVSS 7.5

Authorization Flaw in symfony/security-http (CVE-2026-48489)

Summary

Vulnerability in symfony/security-http (CVE-2026-48489). Confidential information can be exposed externally. Exploitable via DefaultAuthenticationFailureHandler. Mitigation: upgrade to 8.0.13 or later.

Original description

The description as published by the source.

Description

When a firewall is configured with form-login (or any authenticator using DefaultAuthenticationFailureHandler) and the failure_forward: true option, the handler reads the _failure_path parameter from the failing login request and uses it as the path of an internal subrequest dispatched through HttpKernelInterface::SUB_REQUEST.

Symfony's Firewall::onKernelRequest listener intentionally skips subrequests under the assumption they are internally generated and trusted, which also means AccessListener (the listener that evaluates access_control) does not run. Because the attacker controls the target of the subrequest, an unauthenticated POST to the check path with _failure_path=/admin/whatever performs a local request forgery that executes the target controller outside the firewall perimeter and returns its response to the caller.

Applications that follow Symfony's recommended best practice of protecting administrative areas with broad access_control rules (e.g. ^/admin requires ROLE_ADMIN) and expose read-only GET endpoints under that area (data exports, internal APIs, account views) are fully exposed: any such GET route can be read by an unauthenticated attacker without any developer misconfiguration, debug mode, or state-changing GET handler being required.

Resolution

DefaultAuthenticationFailureHandler no longer honors the request-supplied _failure_path parameter when failure_forward is enabled. The subrequest is always di…

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-48489 has been found in symfony/security-http.
Attackers can target a specific entry point like DefaultAuthenticationFailureHandler over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 7.5/10.
What to do: upgrade symfony/security-http to 8.0.13 or later.
If unsure, ask your IT team or search "symfony/security-http CVE-2026-48489" on the vendor's site.

CVE-2026-48489 (symfony/security-http) — CWE-863 / CVSS v3 7.5
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: DefaultAuthenticationFailureHandler / _failure_path / AccessListener / access_control
Patched: 8.0.13 — 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

Incorrect authorization (CWE-863) exists in symfony/security-http. Attackers reach the vulnerable code path via DefaultAuthenticationFailureHandler without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of symfony/security-http. Attack surface: DefaultAuthenticationFailureHandler / _failure_path / AccessListener / access_control.

🔥 Severity

Severity: High (CVSS 7.5/10). Confidential information can be exposed externally.

🔧 How to fix

Update to 8.0.13.

🛡️ 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

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'symfony/security-http' . | grep -v node_modules

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

  2. 2
    Apply patch patch 
    Upgrade symfony/security-http to 8.0.13

    ステージング環境で 8.0.13 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

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

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

Affected packages

composer symfony/security-http
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"8.0.13"}]}]
composer symfony/symfony
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"8.0.13"}]}]
Packagist symfony/security-http
[{"type":"ECOSYSTEM","events":[{"introduced":"8.0.0"},{"fixed":"8.0.13"}]}]
Packagist symfony/symfony
[{"type":"ECOSYSTEM","events":[{"introduced":"8.0.0"},{"fixed":"8.0.13"}]}]

Fix status by distribution

Fixed packages published by each distribution for this CVE

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details