CVE-2017-10974

HIGHNVD 7.58.9▲
EchelonGraph scoreHIGH confidence

Score elevated to 8.9 because EPSS predicts 81% probability of exploitation within the next 30 days (top 0.4% of all CVEs). NVD baseline CVSS 7.5 retained for reference. Confidence: see factors.

Triggered by: EPSS exploit prediction ≥85%
Sources: epss, ghsa, nvd
Elevated
8.9EG
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 81%
CISA-KEV: Not listedEPSS PROB: 81%CVSS: 7.5Exploit: Elevated riskExposed: 0

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

Yaws 1.91 allows Unauthenticated Remote File Disclosure via HTTP Directory Traversal with /%5C../ to port 8080. NOTE: this CVE is only about use of an initial /%5C sequence to defeat traversal protection mechanisms; the initial /%5C sequence was apparently not discussed in earlier research on this product.

CVSS v3
7.5
EG Score
8.9(high)
EG Risk
77(Track)
EG Risk 77/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
Severity89% × 45%
Exploitation81% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
81%
EPSS %ILE
100%
KEV
Not listed

Published

July 7, 2017

Last Modified

June 17, 2026

References (6)

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
yaws—1.91-2—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
yaws—1.91-2—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
yaws—1.91-2—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
yaws—1.91-2—

Weakness Classification(1)

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

Data Freshness Timeline

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

Publicly available exploits

(2 references)

Working exploit code is in the public domain (1 Exploit-DB entry). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • Exploit-DBEDB-42303
    First seen Jul 7, 2017

    Yaws 1.91 - Remote File Disclosure

    Open source ↗
  • Nucleihttp/cves/2017/CVE-2017-10974.yaml
    First seen Jan 1, 2017

    Yaws 1.91 - Local File Inclusion

    Open source ↗

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2017-10974?
CVE-2017-10974 is a high vulnerability published on July 7, 2017. Yaws 1.91 allows Unauthenticated Remote File Disclosure via HTTP Directory Traversal with /%5C../ to port 8080. NOTE: this CVE is only about use of an initial /%5C sequence to defeat traversal protection mechanisms; the initial /%5C sequence was apparently not discussed in earlier research on this…
When was CVE-2017-10974 disclosed?
CVE-2017-10974 was first published in the National Vulnerability Database on July 7, 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-10974 actively exploited?
CVE-2017-10974 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 81% probability of exploitation in the next 30 days, which ranks it in the top 0.4% of all scored CVEs.
What is the CVSS score of CVE-2017-10974?
CVE-2017-10974 has a CVSS v3 base score of 7.5 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 8.9.
How do I remediate CVE-2017-10974?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2017-10974, 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-10974

Explore →

Is Your Infrastructure Affected by CVE-2017-10974?

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

Book a Demo →Browse All CVEs