Skip to content
VulniPulse
Medium6.5Red Hat Linux

CVE-2026-118516: Red Hat Authorization bypass via inconsistent host and path matching

This Red Hat advisory covers CVE-2026-118516.

Open the Red Hat advisory

Key facts

Vendor rating
Medium, CVSS 6.5
CVSS vector
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N · base score 6.3, scored by CheckmarxAttack vector: network. Attack complexity: low. Attack requirements: present. Privileges required: none. User interaction: none. Confidentiality impact on the vulnerable system: low. Integrity impact on the vulnerable system: low. Availability impact on the vulnerable system: none. Confidentiality impact on subsequent systems: none. Integrity impact on subsequent systems: none. Availability impact on subsequent systems: none.
Weakness
  • CWE-436 Interpretation Conflict
  • CWE-863 Incorrect Authorization
EPSS
0.45% chance of exploitation in the next 30 days (39th percentile). FIRST EPSS, .
CISA SSVC
Exploitation: none observed. Automatable: no. Technical impact: partial. CISA, .
CISA KEV
Not listed (catalogue checked )
Affected
< 5.4.56; < 6.4.50; < 7.4.23 and 1 more below
Source published
Listed by VulniPulse

Compiled by VulniPulse from the linked sources. How records are collected and checked.

Affected products & platforms

Red Hat LinuxUnclassified

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. 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.

Text from the source record.

Affected versions
  • < 5.4.56
  • < 6.4.50
  • < 7.4.23
  • < 8.1.11

Official advisory · high-confidence parse· fetched ·verify at source

All Red Hat Linux advisories

Get an email when Red Hat publishes the next one.

See Red Hat's last 90 days first. Live alerts for one product are free for life; every vendor is US$15 a month after a free month.

Alert me about Red Hat