Cloud Foundry GoRouter is vulnerable to cache poisoning

published 2020-02-27 6y ago modified 2026-06-17 4mo ago also EUVD-2020-26580

cvss: 5.3; version 3.0, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 1.0%; EPSS 1.0% chance of exploitation in 30 days, percentile 64%
public exploits: 0; none known

Cloud Foundry Routing Release, versions prior to 0.197.0, contains GoRouter, which allows malicious clients to send invalid headers, causing caching layers to reject subsequent legitimate clients trying to access the app.

Patch / fix

fixed in 1

Cloud Foundry Routing 0.197.0

Is CVE-2020-5401 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

1.04% chance of exploitation in the next 30 days, higher than 64% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by	version	score	vector
CNA	3.0	5.3	CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
NVD	3.1	5.3	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
NVD	2.0	5.0	AV:N/AC:L/Au:N/C:N/I:N/A:P

Affected products

Cloud Foundry Routing

Classification

Weakness

CWE-393 Return of Wrong Status Code
CWE-444 Inconsistent Interpretation of HTTP Requests

References

cloudfoundry.org /blog/cve-2020-5401
vendor-advisory

Sources

CVE List CVE-2020-5401
NVD CVE-2020-5401

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.