SymfonyFramework / library · Sensiolabs
CVE-2026-48489
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedSymfony 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 _failure_path parameter when failure_forward: true was enabled, allowing an unauthenticated failing login request to dispatch a subrequest to access_control-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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe DefaultAuthenticationFailureHandler in Symfony honors the user-supplied _failure_path parameter when failure_forward is enabled, allowing an unauthenticated attacker to craft a login failure request that forwards to access_control-protected GET routes while bypassing firewall listeners.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
SymfonyFramework / library
< 5.4.53>= 6.0.0, < 6.4.41>= 7.0.0, < 7.4.13>= 8.0.0, < 8.0.13CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check Symfony versionRun 'composer show symfony/symfony' or inspect vendor/composer/installed.json to find the installed symfony/symfony versionAffected if The installed version is < 5.4.53, or >= 6.0.0 and < 6.4.41, or >= 7.0.0 and < 7.4.13, or >= 8.0.0 and < 8.0.13
-
Locate security configurationFind the security.yaml or security.php config file in your Symfony project config directoryAffected if File exists - needed for subsequent checks
-
Identify DefaultAuthenticationFailureHandler configurationInspect security config for any firewall entry that uses DefaultAuthenticationFailureHandler or has failure_forward: true configuredAffected if A firewall is configured with failure_forward enabled (failure_forward: true)
-
Check for user-controlled _failure_pathSearch your login form template and authentication handler for usage of the _failure_path request parameter that can be controlled by the userAffected if The login form includes a hidden or visible field named _failure_path or otherwise passes user-supplied input to the failure path
-
Identify access_control protected GET routesReview access_control rules in security config for any GET routes that should be protected by firewall but rely solely on access_controlAffected if There are access_control rules protecting GET routes that would be bypassed by a forward
You are affected if your Symfony version falls within the vulnerable ranges AND you use failure_forward with a user-controlled _failure_path parameter, allowing bypass of access_control rules on GET routes.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped5.4.536.4.417.4.13
Upgrade to Symfony 5.4.53, 6.4.41, 7.4.13, or 8.0.13 or later to patch this access control bypass. If immediate upgrade is not possible, ensure failure_forward is not used with user-controlled _failure_path parameters.
5.4.53, 6.4.41, 7.4.13, or 8.0.13 depending on your current major version branch
- 1. Identify the current Symfony version by checking composer.json or running 'composer show symfony/symfony'
- 2. Determine which version branch you are on (5.x, 6.x, 7.x, or 8.x)
- 3. Run 'composer require symfony/symfony:^5.4.53' for 5.x, 'composer require symfony/symfony:^6.4.41' for 6.x, 'composer require symfony/symfony:^7.4.13' for 7.x, or 'composer require symfony/symfony:^8.0.13' for 8.x
- 4. Run 'composer update symfony/symfony --with-all-dependencies' to apply the upgrade
- 5. Review any authentication-related custom handlers that use the _failure_path parameter
- 6. Test login failure flows to confirm the fix is working correctly
- 7. Verify that access_control restrictions are now enforced on forwarded failure paths
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Symfony
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.0 h
- Testing5.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,464.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-48489 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-48489 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data