CVE-2017-20146

CRITICALNVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 0.7% (51st percentile of EPSS-scored CVEs). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
9.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.7%CVSS: 9.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Usage of the CORS handler may apply improper CORS headers, allowing the requester to explicitly control the value of the Access-Control-Allow-Origin header, which bypasses the expected behavior of the Same Origin Policy.

CVSS v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
59
EG Risk 59/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity98% × 45%
Exploitation1% × 40%
Automatability100% × 15%
CISA SSVC: Track at low or medium mission impact; Attend at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.7%
EPSS %ILE
53rd
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

December 27, 2022

Last Modified

April 11, 2025

Advisory Details (3)

Auto-updated Oct 10, 2026
Patch available. Sources: github_commit, github_pr.
generic

GO-2020-0020 - Go Packages

https://pkg.go.dev/vuln/GO-2020-0020
github_pr Patch Available

Don't return the origin header when configured to *

Patch available: gorilla/handlers v1.3.0 (PR #116 merged 2017-11-01)

https://github.com/gorilla/handlers/pull/116
github_commit Patch Available

commit 90663712d74c (gorilla/handlers)

Patch available: gorilla/handlers v1.3.0 (contains commit 90663712d74c)

https://github.com/gorilla/handlers/commit/90663712d74cb411cbef281bc1e08c19d1a76145

Affected Packages

(5 across 5 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
golang-github-gorilla-handlers—
  • every version up to 1.3.0-1: fixed in 1.3.0-1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
golang-github-gorilla-handlers—
  • every version up to 1.3.0-1: fixed in 1.3.0-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
golang-github-gorilla-handlers—
  • every version up to 1.3.0-1: fixed in 1.3.0-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
golang-github-gorilla-handlers—
  • every version up to 1.3.0-1: fixed in 1.3.0-1
—
Go(1)
PackageVulnerable rangeFix by version rangeDependents
github.com/gorilla/handlers—
  • every version up to 1.3.0: fixed in 1.3.0
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 6× in last 7d / 22× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 147 total refreshes for this CVE.

  1. 2026-10-09 20:02 UTCEPSS rescore
  2. 2026-10-08 16:36 UTCEPSS rescore
  3. 2026-10-07 23:41 UTCEPSS rescore
  4. 2026-10-06 15:12 UTCEPSS rescore
  5. 2026-10-05 17:38 UTCEPSS rescore
  6. 2026-10-04 23:18 UTCEPSS rescore
  7. 2026-10-03 14:21 UTCEPSS rescore
  8. 2026-09-30 14:59 UTCEPSS rescore
  9. 2026-09-30 09:32 UTCEG score recompute
  10. 2026-09-28 13:45 UTCEPSS rescore
  11. 2026-09-27 13:40 UTCEPSS rescore
  12. 2026-09-27 13:40 UTCEPSS rescore
  13. 2026-09-26 15:53 UTCEPSS rescore
  14. 2026-09-24 13:59 UTCEPSS rescore
  15. 2026-09-24 01:06 UTCOSV refresh
  16. 2026-09-18 19:22 UTCEPSS rescore
  17. 2026-09-17 19:22 UTCEPSS rescore
  18. 2026-09-15 03:05 UTCEPSS rescore
  19. 2026-09-15 03:05 UTCEPSS rescore
  20. 2026-09-13 16:42 UTCEPSS rescore
  21. 2026-09-12 14:55 UTCEPSS rescore
  22. 2026-09-11 09:31 UTCEPSS rescore
  23. 2026-09-07 15:56 UTCEPSS rescore
  24. 2026-09-06 13:43 UTCEPSS rescore
  25. 2026-09-05 15:23 UTCEPSS rescore
Show 75 more
  1. 2026-09-04 19:24 UTCOSV refresh
  2. 2026-09-04 13:56 UTCEPSS rescore
  3. 2026-09-02 14:07 UTCEPSS rescore
  4. 2026-09-02 14:07 UTCEPSS rescore
  5. 2026-09-01 03:31 UTCEPSS rescore
  6. 2026-08-30 19:13 UTCEPSS rescore
  7. 2026-08-27 14:21 UTCEPSS rescore
  8. 2026-08-26 14:41 UTCEPSS rescore
  9. 2026-08-25 13:44 UTCEPSS rescore
  10. 2026-08-21 23:44 UTCEPSS rescore
  11. 2026-08-20 22:51 UTCEPSS rescore
  12. 2026-08-19 16:59 UTCEPSS rescore
  13. 2026-08-18 13:43 UTCEPSS rescore
  14. 2026-08-18 06:34 UTCOSV refresh
  15. 2026-08-17 13:42 UTCEPSS rescore
  16. 2026-08-16 14:51 UTCEPSS rescore
  17. 2026-08-16 02:10 UTCEPSS rescore
  18. 2026-08-15 01:26 UTCEPSS rescore
  19. 2026-08-12 13:46 UTCEPSS rescore
  20. 2026-08-09 13:42 UTCEPSS rescore
  21. 2026-08-07 16:22 UTCEPSS rescore
  22. 2026-08-06 13:42 UTCEPSS rescore
  23. 2026-08-05 19:12 UTCEPSS rescore
  24. 2026-08-04 15:05 UTCEPSS rescore
  25. 2026-08-03 01:57 UTCOSV refresh
  26. 2026-08-02 02:23 UTCEPSS rescore
  27. 2026-08-01 04:11 UTCEPSS rescore
  28. 2026-07-30 16:24 UTCEPSS rescore
  29. 2026-07-30 01:26 UTCEPSS rescore
  30. 2026-07-28 15:32 UTCEPSS rescore
  31. 2026-07-26 14:51 UTCEPSS rescore
  32. 2026-07-23 14:15 UTCEPSS rescore
  33. 2026-07-23 01:28 UTCEG score recompute
  34. 2026-07-22 22:08 UTCEG score recompute
  35. 2026-07-22 14:04 UTCEPSS rescore
  36. 2026-07-22 14:04 UTCEPSS rescore
  37. 2026-07-21 15:21 UTCEPSS rescore
  38. 2026-07-21 15:21 UTCEPSS rescore
  39. 2026-07-20 17:04 UTCEPSS rescore
  40. 2026-07-19 14:28 UTCEPSS rescore
  41. 2026-07-19 14:28 UTCEPSS rescore
  42. 2026-07-19 02:26 UTCEPSS rescore
  43. 2026-07-19 02:26 UTCEPSS rescore
  44. 2026-07-18 10:00 UTCEPSS rescore
  45. 2026-07-16 16:59 UTCEPSS rescore
  46. 2026-07-16 16:59 UTCEPSS rescore
  47. 2026-07-16 10:53 UTCOSV refresh
  48. 2026-07-15 16:54 UTCEPSS rescore
  49. 2026-07-15 01:56 UTCEPSS rescore
  50. 2026-07-15 01:56 UTCEPSS rescore
  51. 2026-07-13 22:26 UTCEPSS rescore
  52. 2026-07-12 05:43 UTCEPSS rescore
  53. 2026-07-11 08:24 UTCEPSS rescore
  54. 2026-07-09 19:06 UTCEPSS rescore
  55. 2026-07-08 15:10 UTCEPSS rescore
  56. 2026-07-07 13:42 UTCEPSS rescore
  57. 2026-07-06 16:24 UTCEPSS rescore
  58. 2026-07-06 16:24 UTCEPSS rescore
  59. 2026-07-06 02:20 UTCEPSS rescore
  60. 2026-07-06 02:20 UTCEPSS rescore
  61. 2026-07-05 02:27 UTCEPSS rescore
  62. 2026-07-04 06:28 UTCEPSS rescore
  63. 2026-07-02 16:54 UTCEPSS rescore
  64. 2026-07-01 15:02 UTCEPSS rescore
  65. 2026-06-30 23:19 UTCEPSS rescore
  66. 2026-06-30 23:19 UTCEPSS rescore
  67. 2026-06-29 14:03 UTCEPSS rescore
  68. 2026-06-28 14:04 UTCEPSS rescore
  69. 2026-06-28 10:19 UTCOSV refresh
  70. 2026-06-28 04:53 UTCEPSS rescore
  71. 2026-06-27 03:06 UTCEPSS rescore
  72. 2026-06-27 03:05 UTCEPSS rescore
  73. 2026-06-25 13:47 UTCEPSS rescore
  74. 2026-06-24 14:02 UTCEPSS rescore
  75. 2026-06-24 14:02 UTCEPSS rescore

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2017-20146?
CVE-2017-20146 is a critical vulnerability published on December 27, 2022. Usage of the CORS handler may apply improper CORS headers, allowing the requester to explicitly control the value of the Access-Control-Allow-Origin header, which bypasses the expected behavior of the Same Origin Policy.
When was CVE-2017-20146 disclosed?
CVE-2017-20146 was first published on December 27, 2022, with the most recent update on April 11, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2017-20146 actively exploited?
CVE-2017-20146 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.7% probability of exploitation in the next 30 days (53rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2017-20146?
CVE-2017-20146 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2017-20146?
A fix for CVE-2017-20146 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2017-20146

Explore →

Is Your Infrastructure Affected by CVE-2017-20146?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs