Breaking News: Thousands Of GitHub Accounts Hijacked With wfx-loot CI Secret
Read the Report
Learn How MCP Is Bypassing a Decade of Cloud Security Best Practices
Read the Report
Are you exposed? Connect a repo in minutes.
Scan your repos free

CVE-2026-118516

The Symfony Routing componentsCompiledUrlMatcher and UrlMatcherinterpr ...

Overview

Published
4 Nov 2026
Modified
9 Nov 2026
Medium CVE
2 Registry packages
1 OS packages
2 Linux distributions
Yes Fix available
CVSS score Medium, no score

Description

The Symfony Routing components CompiledUrlMatcher and UrlMatcher interpret the host and path information differently, allowing path-based authorization rules to be bypassed in Symfony versions prior to 5.4.56, 6.x prior to 6.4.50, 7.x prior to 7.4.23, and 8.x prior to 8.1.11.

For routes that define a host, CompiledUrlMatcher matches the string $host.'.'.$pathinfo against the host regular expression followed by the path regular expression, while UrlMatcher matches the host and the path separately. A host placeholder can therefore  match /, and consume the beginning of the path, so the request is routed to a controller, while UrlMatcher  would find no route. Rules that look at the path, such as access_control entries and firewall patterns, are evaluated against the actual request path, so they do not apply while the controller of the route runs, potentially allowing an unauthenticated request to reach a protected controller. For example, with the route /admin/report/{id}, the host app.{domain} and the rule access_control: [{ path: ^/admin, roles: ROLE_ADMIN }], an anonymous request for /admin/report/1 is sent to the login page. A request with the Host header app and path /x./admin/report/1 instead reaches the controller, with domain="/x". With the required domain: .+, the real hostname works: app.example.com and /x./admin/report/1 match with domain="example.com./x".

Applications are affected if they have routes with host placeholders protected by path-based rules. With the default requirement, the Host header must be the host of the route without its last labels, such as app: framework.trusted_hosts blocks that, while a web server that only serves known names may not, for instance, Nginx passing the raw Host header to FastCGI for a request line that carries an absolute URI. If the requirement accepts /, such as .+, a real hostname works, and trusted_hosts does not help.

Source: OX vulnerability database

Severity

MEDIUM

No CVSS vector in the source. Severity comes from the advisory.

Weakness: CWE-436, CWE-863

Affected packages · 2

Packages affected by CVE-2026-118516
EcosystemPackageVulnerableFixed in
Composer (PHP) symfony/routing >=6.0.0, <6.1.0>=7.2.0, <7.3.0>=8.1.0, <8.1.11>=4.2.0, <4.3.0>=4.3.0, <4.4.0+16 more No fix yet
Composer (PHP) symfony/symfony >=5.1.0, <5.2.0>=6.4.0, <6.4.50>=7.3.0, <7.4.0>=7.4.0, <7.4.23>=8.1.0, <8.1.11+16 more No fix yet

Open a package to see all its vulnerabilities.

Operating systems · 5 fixes

debian 4 releases · 1 package

affected 2 fixed 2
symfony
debian fixes for CVE-2026-118516
ReleasePackageFixed in
11 symfony affected
12 symfony affected
13 symfony 6.4.50+dfsg-0+deb13u1
14 symfony 7.4.23+dfsg-1

echo 1 release · 1 package

fixed 1
symfony
echo fixes for CVE-2026-118516
ReleasePackageFixed in
symfony 6.4.50+dfsg-0+deb13u1

References

OX Radar and Response Center

Find threats in your stack.

OX Radar can check high-priority threats, like critical package CVEs, against your context.

Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.