CVE-2026-48489: Symfony: Security Firewall Bypass via failure_forward Subrequest: Unauthenticated Access to access_control-Protected GET Routes

Published Jun 15, 2026
·
Updated

Description

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

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 accesscontrol) does not run. Because the attacker controls the target of the subrequest, an unauthenticated POST to the check path with failurepath=/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 accesscontrol rules (e.g. ^/admin requires ROLEADMIN) 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 failurepath parameter when failureforward is enabled. The subrequest is always dispatched to the configured failurepath option (defaulting to loginpath), which is set by the application owner and not by the request. The redirect branch (failureforward: false) is unchanged because redirects re-enter the firewall on the next request and are not subject to this bypass.

The patch for this issue is available here for branch 5.4.

Credits

Symfony would like to thank Nguyen Ngoc Toan Thang (@a-tt-om) and Tran Quoc Tri Trung (@teebow1e) for reporting the issue, and Nicolas Grekas for providing the fix.

Other sources

Symfony is a PHP framework for web and console applications and a set of reusable PHP components. Prior to 5.4.53, 6.4.41, 7.4.13, and 8.0.13, DefaultAuthenticationFailureHandler honored the request-supplied failurepath parameter when failureforward: true was enabled, allowing an unauthenticated failing login request to dispatch a subrequest to accesscontrol-protected GET routes that skipped firewall listeners. This issue is fixed in versions 5.4.53, 6.4.41, 7.4.13, and 8.0.13.

MITRE

Affected Software

12 affected componentsFixes available
composer/symfony/symfony>=8.0.0<8.0.13
8.0.13
composer/symfony/symfony>=7.0.0<7.4.13
7.4.13
composer/symfony/symfony>=6.0.0<6.4.41
6.4.41
composer/symfony/security-http>=8.0.0<8.0.13
8.0.13
composer/symfony/security-http>=7.0.0<7.4.13
7.4.13
composer/symfony/security-http>=6.0.0<6.4.41
6.4.41
composer/symfony/symfony<5.4.53
5.4.53
composer/symfony/security-http<5.4.53
5.4.53
SensioLabs Symfony<5.4.53
SensioLabs Symfony>=6.0.0<6.4.41
SensioLabs Symfony>=7.0.0<7.4.13
SensioLabs Symfony>=8.0.0<8.0.13

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade composer/symfony/symfony to a version that resolves this vulnerability.

    Fixed in 8.0.13
  2. Upgrade

    Upgrade composer/symfony/symfony to a version that resolves this vulnerability.

    Fixed in 7.4.13
  3. Upgrade

    Upgrade composer/symfony/symfony to a version that resolves this vulnerability.

    Fixed in 6.4.41
  4. Upgrade

    Upgrade composer/symfony/security-http to a version that resolves this vulnerability.

    Fixed in 8.0.13
  5. Upgrade

    Upgrade composer/symfony/security-http to a version that resolves this vulnerability.

    Fixed in 7.4.13
  6. Upgrade

    Upgrade composer/symfony/security-http to a version that resolves this vulnerability.

    Fixed in 6.4.41
  7. Upgrade

    Upgrade composer/symfony/symfony to a version that resolves this vulnerability.

    Fixed in 5.4.53
  8. Upgrade

    Upgrade composer/symfony/security-http to a version that resolves this vulnerability.

    Fixed in 5.4.53
  9. Upgrade

    Upgrade Symfony to a version that resolves this vulnerability.

    Fixed in 5.4.53
  10. Upgrade

    Upgrade Symfony to a version that resolves this vulnerability.

    Fixed in 6.4.41
  11. Upgrade

    Upgrade Symfony to a version that resolves this vulnerability.

    Fixed in 7.4.13
  12. Upgrade

    Upgrade Symfony to a version that resolves this vulnerability.

    Fixed in 8.0.13

Event History

Jun 15, 2026
Advisory Published
via GitHub·05:28 PM
Data Sourced
via GitHub·05:28 PM
DescriptionWeaknessAffected Software
Jul 14, 2026
CVE Published
via MITRE·07:14 PM
Data Sourced
via MITRE·07:14 PM
DescriptionWeakness
Data Sourced
via NVD·08:17 PM
RemedyDescriptionSeverityWeaknessAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-48489?

The severity of CVE-2026-48489 is rated at 71.

2

How do I fix CVE-2026-48489?

To fix CVE-2026-48489, update to the latest version of Symfony that addresses this vulnerability.

3

What systems are affected by CVE-2026-48489?

CVE-2026-48489 affects Symfony applications using the `form-login` feature with `DefaultAuthenticationFailureHandler` configured.

4

What kind of attack can exploit CVE-2026-48489?

CVE-2026-48489 can potentially be exploited to redirect users to arbitrary paths through manipulated login requests.

5

Is CVE-2026-48489 publicly known?

Yes, CVE-2026-48489 was publicly disclosed on June 15, 2026.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203