https://db.gcve.eu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Wed, 11 Nov 2026 07:19:34 +0000 https://db.gcve.eu/vuln/cve-2026-118516 <p><strong>Affected:</strong> sensiolabs symfony</p> <p>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.</p> <p>For routes that define a host, CompiledUrlMatcher matches the string $host.&#39;.&#39;.$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=&#34;/x&#34;. With the required domain: .+, the real hostname works: app.example.com and /x./admin/report/1 match with domain=&#34;example.com./x&#34;.</p> <p>Applications are affected if they have routes with host placeholders protected by path-based rules. With…</p> <p><strong>Affected:</strong> sensiolabs symfony</p> <p>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.</p> <p>For routes that define a host, CompiledUrlMatcher matches the string $host.&#39;.&#39;.$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=&#34;/x&#34;. With the required domain: .+, the real hostname works: app.example.com and /x./admin/report/1 match with domain=&#34;example.com./x&#34;.</p> <p>Applications are affected if they have routes with host placeholders protected by path-based rules. With…</p> https://db.gcve.eu/vuln/cve-2026-118516