# CVE-2025-64500: Symfony's incorrect parsing of PATH_INFO can lead to limited authorization bypass

Source: https://junglewise.ai/threats/cve-2025-64500-symfony-s-incorrect-parsing-of-path-info-can-lead-to-limited  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2025-11-12  
License: CC BY 4.0 with a link back

CVE-2025-64500 · Severity: high · CVSS 7.3 · Published 2025-11-12

Symfony is a PHP framework for web and console applications and a set of reusable PHP components. Symfony's HttpFoundation component defines an object-oriented layer for the HTTP specification. Starting in version 2.0.0 and prior to version 5.4.50, 6.4.29, and 7.3.7, 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. Starting in versions 5.4.50, 6.4.29, and 7.3.7, the `Request` class now ensures that URL paths always start with a `/`.

Technologies: [symfony/http-foundation (Packagist)](https://junglewise.ai/threats/technologies/symfony-http-foundation), [symfony/symfony (Packagist)](https://junglewise.ai/threats/technologies/symfony-symfony). Vendors: [Packagist](https://junglewise.ai/threats/vendors/packagist).

## Quick answers

**Is CVE-2025-64500 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2025-64500 being exploited in the wild.

**How severe is CVE-2025-64500?** High severity, with a CVSS score of 7.3, published 12 November 2025.

**Which products and versions are affected?** symfony/http-foundation (Packagist) ECOSYSTEM:introduced=0,fixed=5.4.50; symfony/symfony (Packagist) ECOSYSTEM:introduced=2.0.0,fixed=5.4.50.

**Is there a fix for CVE-2025-64500?** Yes. symfony/http-foundation (Packagist): upgrade to 5.4.50 or later; symfony/symfony (Packagist): upgrade to 5.4.50 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**Am I affected by CVE-2025-64500?** Check whether you run symfony/http-foundation (Packagist), symfony/symfony (Packagist), Sensiolabs Httpfoundation or one of the others listed at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## How to fix

- symfony/http-foundation (Packagist): upgrade to 5.4.50 or later

  ```sh
  composer require symfony/http-foundation:^5.4.50
  ```

- symfony/symfony (Packagist): upgrade to 5.4.50 or later

  ```sh
  composer require symfony/symfony:^5.4.50
  ```


## Affected products

- symfony/http-foundation (Packagist) ECOSYSTEM:introduced=0,fixed=5.4.50
- symfony/symfony (Packagist) ECOSYSTEM:introduced=2.0.0,fixed=5.4.50
- Sensiolabs Httpfoundation
- Sensiolabs Symfony

## Identifiers

- CVE-2025-64500
- GHSA-3rg7-wf37-54rm

## Related threats

- [Symfony YAML stack exhaustion in inline lexer](https://junglewise.ai/threats/cve-2026-109413-in-symfony-yaml-prior-to-versions-5-4-54-6-4-45-7-4-18-and-8-1-6)
- [Symfony HTTP Foundation ReDoS in HeaderUtils::split()](https://junglewise.ai/threats/cve-2026-108082-symfony-is-a-php-framework-for-web-and-console-applications-and)
- [Symfony Routing improper dot-segment encoding in UrlGenerator](https://junglewise.ai/threats/cve-2026-48784-symfony-routing-improper-dot-segment-encoding-in-urlgenerator)
- [Symfony HtmlSanitizer XSS via incomplete URL attribute sanitization](https://junglewise.ai/threats/cve-2026-48761-symfony-htmlsanitizer-xss-via-incomplete-url-attribute)
- [Symfony HtmlSanitizer visual spoofing via percent-encoded BiDi characters](https://junglewise.ai/threats/cve-2026-48760-symfony-htmlsanitizer-visual-spoofing-via-percent-encoded-bidi)
