Skip to content

Symfony's incorrect parsing of PATH_INFO can lead to limited authorization bypass

High severity GitHub Reviewed Published Nov 12, 2025 in symfony/symfony • Updated Nov 15, 2025

Package

composer symfony/http-foundation (Composer)

Affected versions

< 5.4.50
>= 6.0.0, < 6.4.29
>= 7.0.0, < 7.3.7

Patched versions

5.4.50
6.4.29
7.3.7
composer symfony/symfony (Composer)
>= 2.0.0, < 5.4.50
>= 6.0.0, < 6.4.29
>= 7.0.0, < 7.3.7
5.4.50
6.4.29
7.3.7

Description

Description

The Request class improperly interprets some PATH_INFO in a way that leads to representing some URLs with a path that doesn't start with a /. This can allow bypassing some access control rules that are built with this /-prefix assumption.

Resolution

The Request class now ensures that URL paths always start with a /.

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

Credits

We would like to thank Andrew Atkinson for discovering the issue, Chris Smith for reporting it and Nicolas Grekas for providing the fix.

References

@nicolas-grekas nicolas-grekas published to symfony/symfony Nov 12, 2025
Published to the GitHub Advisory Database Nov 12, 2025
Reviewed Nov 12, 2025
Published by the National Vulnerability Database Nov 12, 2025
Last updated Nov 15, 2025

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L

EPSS score

Exploit Prediction Scoring System (EPSS)

This score estimates the probability of this vulnerability being exploited within the next 30 days. Data provided by FIRST.
(69th percentile)

Weaknesses

Use of Non-Canonical URL Paths for Authorization Decisions

The product defines policy namespaces and makes authorization decisions based on the assumption that a URL is canonical. This can allow a non-canonical URL to bypass the authorization. Learn more on MITRE.

CVE ID

CVE-2025-64500

GHSA ID

GHSA-3rg7-wf37-54rm

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.