SummaryAI-written · claude-haiku-5-5AI-written · claude-haiku-5-5Written by a language model from the source data on this page. Not reviewed by a person. Generated 29 Oct 2026.
The flaw is in the HttpFoundation component of Symfony (Request::prepareRequestUri()), where support for legacy IIS headers X-Original-URL and X-Rewrite-URL is unverified and allows the request path to be overridden even when the server is not running IIS. An attacker who can send HTTP requests to an affected application can supply one of these headers to change the path being processed, which can be used for attacks such as web cache poisoning, with no authentication or user interaction indicated as required.
Official description · CVE.orgSource dataSource dataCopied from an authoritative feed: NVD, CVE.org, CISA KEV, FIRST EPSS or MITRE CTID mappings, or labelled by the annotators of a published dataset. Copied from CVE.org.
An issue was discovered in Http Foundation in Symfony 2.7.0 through 2.7.48, 2.8.0 through 2.8.43, 3.3.0 through 3.3.17, 3.4.0 through 3.4.13, 4.0.0 through 4.0.13, and 4.1.0 through 4.1.2. It arises from support for a (legacy) IIS header that lets users override the path in the request URL via the X-Original-URL or X-Rewrite-URL HTTP request header. These headers are designed for IIS support, but it's not verified that the server is in fact running IIS, which means anybody who can send these requests to an application can trigger this. This affects \Symfony\Component\HttpFoundation\Request::prepareRequestUri() where X-Original-URL and X_REWRITE_URL are both used. The fix drops support for these methods so that they cannot be used as attack vectors such as web cache poisoning.
Priority scorePatchfirst’s 0 to 100 ranking. It adds points for CISA KEV listing, ransomware use, EPSS, threat reports, public exploit code and CVSS. Every CVE page shows the breakdown.Breakdown
19.8 / 100
Exploited
Not confirmed
Reports
0
Tactics
0/15
Exploitation timelineDated milestones for a CVE: when it was disclosed, when exploit code became public, when exploitation was confirmed, and when threat reports named it.
Disclosed on 3 Aug 2018. No public exploit code or confirmed exploitation is recorded.
Am I affected? What do I upgrade to?
From GitHub Security Advisories and OSVSourceSource dataCopied from an authoritative feed: NVD, CVE.org, CISA KEV, FIRST EPSS or MITRE CTID mappings, or labelled by the annotators of a published dataset. GitHub Security Advisories and OSV.
2 packages in 1 ecosystem. Main package: symfony/symfony.
Set the version to 4.1.3 or later in your composer.json.
The first fix for CVE-2018-14773.
Affected versions, by release line
If you run
Upgrade to
4.1.0 up to 4.1.3
4.1.3
4.0.0 up to 4.0.14
4.0.14
3.4.0 up to 3.4.14
3.4.14
3.0.0 up to 3.3.18
3.3.18
2.8.0 up to 2.8.44
2.8.44
2.7.0 up to 2.7.49
2.7.49
“Up to” means the second version is the fix and is not affected.
Other packages that bundle this code (1)
Forks, repackagings and products that include the affected code. Each has its own fixed version.
Packagistsymfony/http-foundation
Affected: 4.1.0 up to 4.1.3; 4.0.0 up to 4.0.14; 3.4.0 up to 3.4.14; 3.0.0 up to 3.3.18; 2.8.0 up to 2.8.44; 2.7.0 up to 2.7.49Upgrade to 4.1.3 or later (older lines: 4.0.14, 3.4.14, 3.3.18, 2.8.44, 2.7.49)