{"id":"CVE-2020-25017","url":"https://www.cyber-defence.io/tools/cve/CVE-2020-25017","generatedAt":"2026-10-27T22:25:59.488Z","title":"Envoy through 1.15.0 only considers the first value when multiple header values are present for some HTTP headers.","description":"Envoy through 1.15.0 only considers the first value when multiple header values are present for some HTTP headers. Envoy’s setCopy() header map API does not replace all existing occurences of a non-inline header.","published":"2020-10-01T17:15:13.000Z","lastModified":"2026-06-17T03:06:15.000Z","status":"Modified","sourceIdentifier":"cve@mitre.org","cvss":{"version":"3.1","score":8.3,"severity":"HIGH","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:L"},"cwe":[],"affected":["envoyproxy/envoy"],"epss":{"score":0.01317,"percentile":0.70581,"date":"2026-10-26","history":[]},"kev":{"listed":false},"exploits":{"count":0,"verified":false,"firstPublished":null,"source":"Exploit-DB (https://gitlab.com/exploit-database/exploitdb)","entries":[]},"verdict":{"level":"high","text":"High impact if exploited, but EPSS currently rates exploitation as unlikely (1.32%). Schedule it in the normal patch cycle and watch for a rise in EPSS or a public exploit."},"changes":[],"references":[{"url":"https://github.com/envoyproxy/envoy/security/advisories/GHSA-2v25-cjjq-5f4w","tags":["Exploit","Third Party Advisory"],"source":"cve@mitre.org"},{"url":"https://groups.google.com/forum/#%21forum/envoy-security-announce","source":"cve@mitre.org"},{"url":"https://github.com/envoyproxy/envoy/security/advisories/GHSA-2v25-cjjq-5f4w","tags":["Exploit","Third Party Advisory"],"source":"af854a3a-2127-422b-91ae-364da2661108"},{"url":"https://groups.google.com/forum/#%21forum/envoy-security-announce","source":"af854a3a-2127-422b-91ae-364da2661108"}],"sources":{"nvd":"https://nvd.nist.gov/vuln/detail/CVE-2020-25017","epss":"https://www.first.org/epss/","kev":"https://www.cisa.gov/known-exploited-vulnerabilities-catalog","exploitdb":"https://www.exploit-db.com/"},"licence":"CC BY 4.0 — link back to the CVE Explorer if you publish the results; upstream data remains subject to its own terms."}