CVE-2017-11173

HIGHNVD 8.88.8—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.8 under NVD CVSS v3. EPSS exploit probability: 2.3%, top 18% of all CVEs by exploit prediction. 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
8.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 2%CVSS: 8.8Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Missing anchor in generated regex for rack-cors before 0.4.1 allows a malicious third-party site to perform CORS requests. If the configuration were intended to allow only the trusted example.com domain name and not the malicious example.net domain name, then example.com.example.net (as well as example.com-example.net) would be inadvertently allowed.

CVSS v3
8.8
EG Score
8.8(medium)
EG Risk
45(Track)
EG Risk 45/100SSVC: Track

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
Severity88% × 45%
Exploitation2% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
2%
EPSS %ILE
83%
KEV
Not listed

Published

July 13, 2017

Last Modified

June 17, 2026

Advisory Details (4)

Auto-updated Aug 16, 2026
Patch available. Sources: github_commit.
generic

Packet Storm Security

https://packetstormsecurity.com/files/143345/rack-cors-Missing-Anchor.html
github_commit

commit 42ebe6caa8e8 (cyu/rack-cors)

Fix landed in cyu/rack-cors commit 42ebe6caa8e8 — awaiting tagged release

https://github.com/cyu/rack-cors/commit/42ebe6caa8e85ffa9c8a171bda668ba1acc7a5e6
generic

Debian -- The Universal Operating System

http://www.debian.org/security/2017/dsa-3931
generic Patch Available

Full Disclosure: CVE-2017-11173 Missing anchor in generated regex for rack-cors before 0.4.1 allows a malicious third-party site to perform CORS requests

http://seclists.org/fulldisclosure/2017/Jul/22

Affected Packages

(6 across 6 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
ruby-rack-cors—0.4.1-1—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
ruby-rack-cors—0.4.1-1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
ruby-rack-cors—0.4.1-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
ruby-rack-cors—0.4.1-1—
Debian:9(1)
PackageVulnerable rangeFixed inDependents
ruby-rack-cors0.4.0-10.4.0-1+deb9u1—
RubyGems(1)
PackageVulnerable rangeFixed inDependents
rack-cors0.1.0 ... 0.4.0 (13 versions)0.4.1—

Data Freshness Timeline

(refreshed 3× in last 7d / 21× 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 141 total refreshes for this CVE.

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

Related CVEs(same product)

Same product

2 shown

Debian:11:ruby-rack-cors · RubyGems:rack-cors

Frequently asked(5)

What is CVE-2017-11173?
CVE-2017-11173 is a high vulnerability published on July 13, 2017. Missing anchor in generated regex for rack-cors before 0.4.1 allows a malicious third-party site to perform CORS requests. If the configuration were intended to allow only the trusted example.com domain name and not the malicious example.net domain name, then example.com.example.net (as well as…
When was CVE-2017-11173 disclosed?
CVE-2017-11173 was first published in the National Vulnerability Database on July 13, 2017, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2017-11173 actively exploited?
CVE-2017-11173 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 2% probability of exploitation in the next 30 days, which ranks it in the top 17.1% of all scored CVEs.
What is the CVSS score of CVE-2017-11173?
CVE-2017-11173 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2017-11173?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2017-11173, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2017-11173?

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

Book a Demo →Browse All CVEs