CVE-2017-16040

HIGHNVD 8.18.1—
EchelonGraph scoreMEDIUM confidence

Score 8.1 from GitHub Security Advisory (severity: HIGH) published 2020-09-01. NVD baseline CVSS 8.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
8.1
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 2%CVSS: 8.1Exploit: NoneExposed: 0

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

gfe-sass is a library for promises (CommonJS/Promises/A,B,D) gfe-sass downloads resources over HTTP, which leaves it vulnerable to MITM attacks. It may be possible to cause remote code execution (RCE) by swapping out the requested resources with an attacker controlled copy if the attacker is on the network or positioned in between the user and the remote server.

CVSS v3
8.1
EG Score
8.1(medium)
EPSS
74.5%
KEV
Not listed

Published

June 4, 2018

Last Modified

November 21, 2024

References (2)

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
npmgfe-sass—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFixed inDependents
gfe-sass———

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 10× in last 7d / 36× 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.

  1. 2026-07-22 14:04 UTCEPSS rescore
  2. 2026-07-21 15:21 UTCEPSS rescore
  3. 2026-07-21 15:21 UTCEPSS rescore
  4. 2026-07-20 17:04 UTCEPSS rescore
  5. 2026-07-20 17:04 UTCEPSS rescore
  6. 2026-07-19 02:26 UTCEPSS rescore
  7. 2026-07-19 02:26 UTCEPSS rescore
  8. 2026-07-18 10:00 UTCEPSS rescore
  9. 2026-07-16 16:59 UTCEPSS rescore
  10. 2026-07-16 16:59 UTCEPSS rescore
  11. 2026-07-15 16:54 UTCEPSS rescore
  12. 2026-07-15 16:54 UTCEPSS rescore
  13. 2026-07-15 01:56 UTCEPSS rescore
  14. 2026-07-13 22:26 UTCEPSS rescore
  15. 2026-07-13 06:09 UTCEPSS rescore
  16. 2026-07-12 05:43 UTCEPSS rescore
  17. 2026-07-11 08:24 UTCEPSS rescore
  18. 2026-07-09 19:06 UTCEPSS rescore
  19. 2026-07-08 15:10 UTCEPSS rescore
  20. 2026-07-07 13:42 UTCEPSS rescore
  21. 2026-07-06 16:24 UTCEPSS rescore
  22. 2026-07-06 02:20 UTCEPSS rescore
  23. 2026-07-05 02:27 UTCEPSS rescore
  24. 2026-07-04 06:28 UTCEPSS rescore
  25. 2026-07-01 15:02 UTCEPSS rescore
Show 56 more
  1. 2026-07-01 15:02 UTCEPSS rescore
  2. 2026-06-30 23:19 UTCEPSS rescore
  3. 2026-06-30 23:19 UTCEPSS rescore
  4. 2026-06-29 14:03 UTCEPSS rescore
  5. 2026-06-28 14:04 UTCEPSS rescore
  6. 2026-06-28 04:53 UTCEPSS rescore
  7. 2026-06-27 03:05 UTCEPSS rescore
  8. 2026-06-25 13:47 UTCEPSS rescore
  9. 2026-06-25 13:47 UTCEPSS rescore
  10. 2026-06-24 14:02 UTCEPSS rescore
  11. 2026-06-23 21:30 UTCEPSS rescore
  12. 2026-06-22 14:23 UTCEPSS rescore
  13. 2026-06-22 14:23 UTCEPSS rescore
  14. 2026-06-21 14:54 UTCEPSS rescore
  15. 2026-06-21 14:54 UTCEPSS rescore
  16. 2026-06-21 01:57 UTCEPSS rescore
  17. 2026-06-21 01:57 UTCEPSS rescore
  18. 2026-06-19 19:23 UTCEPSS rescore
  19. 2026-06-19 19:23 UTCEPSS rescore
  20. 2026-06-18 17:50 UTCEPSS rescore
  21. 2026-06-17 17:50 UTCEPSS rescore
  22. 2026-06-16 17:50 UTCEPSS rescore
  23. 2026-06-15 17:45 UTCEPSS rescore
  24. 2026-06-14 23:14 UTCEPSS rescore
  25. 2026-06-14 23:14 UTCEPSS rescore
  26. 2026-06-13 22:57 UTCEPSS rescore
  27. 2026-06-12 23:09 UTCEPSS rescore
  28. 2026-06-11 13:57 UTCEPSS rescore
  29. 2026-06-10 22:15 UTCEPSS rescore
  30. 2026-06-08 14:14 UTCEPSS rescore
  31. 2026-06-07 15:22 UTCEPSS rescore
  32. 2026-06-07 15:22 UTCEPSS rescore
  33. 2026-06-06 13:45 UTCEPSS rescore
  34. 2026-06-06 13:45 UTCEPSS rescore
  35. 2026-06-05 22:44 UTCEPSS rescore
  36. 2026-06-05 06:08 UTCEPSS rescore
  37. 2026-06-05 06:08 UTCEPSS rescore
  38. 2026-06-04 13:10 UTCEPSS rescore
  39. 2026-06-04 13:10 UTCEPSS rescore
  40. 2026-06-02 20:11 UTCEPSS rescore
  41. 2026-06-02 20:11 UTCEPSS rescore
  42. 2026-06-01 13:49 UTCEPSS rescore
  43. 2026-06-01 13:49 UTCEPSS rescore
  44. 2026-05-31 22:28 UTCEPSS rescore
  45. 2026-05-31 00:14 UTCEPSS rescore
  46. 2026-05-29 13:41 UTCEPSS rescore
  47. 2026-05-28 13:42 UTCEPSS rescore
  48. 2026-05-28 13:42 UTCEPSS rescore
  49. 2026-05-28 07:23 UTCEG score recompute
  50. 2026-05-28 07:23 UTCGHSA enrichment
  51. 2026-05-27 13:38 UTCEPSS rescore
  52. 2026-05-27 13:38 UTCEPSS rescore
  53. 2026-05-26 13:42 UTCEPSS rescore
  54. 2026-05-26 13:42 UTCEPSS rescore
  55. 2026-05-26 07:17 UTCEPSS rescore
  56. 2026-05-26 07:17 UTCEPSS rescore

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2017-16040?
CVE-2017-16040 is a high vulnerability published on June 4, 2018. gfe-sass is a library for promises (CommonJS/Promises/A,B,D) gfe-sass downloads resources over HTTP, which leaves it vulnerable to MITM attacks. It may be possible to cause remote code execution (RCE) by swapping out the requested resources with an attacker controlled copy if the attacker is on the…
When was CVE-2017-16040 disclosed?
CVE-2017-16040 was first published in the National Vulnerability Database on June 4, 2018, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2017-16040 actively exploited?
CVE-2017-16040 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 74.5% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2017-16040?
CVE-2017-16040 has a CVSS v3 base score of 8.1 (NVD).
How do I remediate CVE-2017-16040?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2017-16040, 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-16040

Explore →

Is Your Infrastructure Affected by CVE-2017-16040?

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

Start Free Scan →Browse All CVEs