CVE-2017-7668

HIGHNVD 7.58.2▲
EchelonGraph scoreHIGH confidence

Score elevated to 8.2 because EPSS predicts 57% probability of exploitation within the next 30 days (top 1.0% 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.2EG
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • 43 internet-exposed hosts are running an affected version right now
  • High exploitation likelihood — EPSS 57%
CISA-KEV: Not listedEPSS PROB: 57%CVSS: 7.5Exploit: Elevated riskExposed: 43

A fix is available — apply it.

The HTTP strict parsing changes added in Apache httpd 2.2.32 and 2.4.24 introduced a bug in token list parsing, which allows ap_find_token() to search past the end of its input string. By maliciously crafting a sequence of request headers, an attacker may be able to cause a segmentation fault, or to force ap_find_token() to return an incorrect value.

Live · internet exposure

43 internet-exposed hosts are running an affected version of CVE-2017-7668 right now.

across 18 countries (United States, Germany, France, Switzerland, Argentina)top: http_server
See the live KEV-Exposure radar →Found passively from public internet-scan data — aggregate, host-redacted.

EchelonGraph is the only CVE feed that fuses live vulnerability intelligence with its own live internet-exposure radar — so you see not just that a CVE is exploited, but how much of the internet is exposed to it right now.

CVSS v3
7.5
EG Score
8.2(high)
EG Risk
64(Track)
EG Risk 64/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
Severity82% × 45%
Exploitation57% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
57%
EPSS %ILE
99%
KEV
Not listed

Published

June 20, 2017

Last Modified

June 17, 2026

References (70)

Patch Availability(6)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntuapache2-bin (2.4.25-3ubuntu2.1) @ zesty2026-05-22ubuntu
ubuntuapache2.2-bin (2.2.22-1ubuntu1.12) @ precise2026-05-22ubuntu
redhathttpd-0:2.4.6-40.el7_2.62017-11-13redhat
redhathttpd-0:2.4.6-45.el7_3.52017-11-13redhat
redhathttpd24-httpd-0:2.4.25-9.el7.12017-08-16redhat
redhathttpd-0:2.4.6-67.el7_4.22017-08-15redhat

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

(29 across 29 ecosystems)
Alpine:v3.10(1)
PackageVulnerable rangeFixed inDependents
apache2—2.4.26-r0—
Alpine:v3.11(1)
PackageVulnerable rangeFixed inDependents
apache2—2.4.26-r0—
Alpine:v3.12(1)
PackageVulnerable rangeFixed inDependents
apache2—2.4.26-r0—
Alpine:v3.13(1)
PackageVulnerable rangeFixed inDependents
apache2—2.4.26-r0—
Alpine:v3.14(1)
PackageVulnerable rangeFixed inDependents
apache2—2.4.26-r0—
Alpine:v3.15(1)
PackageVulnerable rangeFixed inDependents
apache2—2.4.26-r0—
Alpine:v3.16(1)
PackageVulnerable rangeFixed inDependents
apache2—2.4.26-r0—
Alpine:v3.17(1)
PackageVulnerable rangeFixed inDependents
apache2—2.4.26-r0—
Alpine:v3.18(1)
PackageVulnerable rangeFixed inDependents
apache2—2.4.26-r0—
Alpine:v3.19(1)
PackageVulnerable rangeFixed inDependents
apache2—2.4.26-r0—
Alpine:v3.20(1)
PackageVulnerable rangeFixed inDependents
apache2—2.4.26-r0—
Alpine:v3.21(1)
PackageVulnerable rangeFixed inDependents
apache2—2.4.26-r0—
Alpine:v3.22(1)
PackageVulnerable rangeFixed inDependents
apache2—2.4.26-r0—
Alpine:v3.23(1)
PackageVulnerable rangeFixed inDependents
apache2—2.4.26-r0—
Alpine:v3.24(1)
PackageVulnerable rangeFixed inDependents
apache2—2.4.26-r0—
Alpine:v3.3(1)
PackageVulnerable rangeFixed inDependents
apache2—2.4.26-r0—
Alpine:v3.4(1)
PackageVulnerable rangeFixed inDependents
apache2—2.4.26-r0—
Alpine:v3.5(1)
PackageVulnerable rangeFixed inDependents
apache2—2.4.26-r0—
Alpine:v3.6(1)
PackageVulnerable rangeFixed inDependents
apache2—2.4.26-r0—
Alpine:v3.7(1)
PackageVulnerable rangeFixed inDependents
apache2—2.4.26-r0—
Alpine:v3.8(1)
PackageVulnerable rangeFixed inDependents
apache2—2.4.26-r0—
Alpine:v3.9(1)
PackageVulnerable rangeFixed inDependents
apache2—2.4.26-r0—
Debian:11(1)
PackageVulnerable rangeFixed inDependents
apache2—2.4.25-4—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
apache2—2.4.25-4—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
apache2—2.4.25-4—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
apache2—2.4.25-4—
Debian:7(1)
PackageVulnerable rangeFixed inDependents
apache22.2.22-13 ... 2.2.22-13+deb7u8 (9 versions)2.2.22-13+deb7u9—
Debian:8(1)
PackageVulnerable rangeFixed inDependents
apache22.4.10-10 ... 2.4.10-10+deb8u8 (9 versions)2.4.10-10+deb8u9—
Debian:9(1)
PackageVulnerable rangeFixed inDependents
apache22.4.25-32.4.25-3+deb9u1—

Weakness Classification(2)

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

All Vendor Advisories

(6)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 4× in last 7d / 16× 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 112 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2017-7668?
CVE-2017-7668 is a high vulnerability published on June 20, 2017. The HTTP strict parsing changes added in Apache httpd 2.2.32 and 2.4.24 introduced a bug in token list parsing, which allows apfindtoken() to search past the end of its input string. By maliciously crafting a sequence of request headers, an attacker may be able to cause a segmentation fault, or to…
When was CVE-2017-7668 disclosed?
CVE-2017-7668 was first published in the National Vulnerability Database on June 20, 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-7668 actively exploited?
CVE-2017-7668 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 57% probability of exploitation in the next 30 days, which ranks it in the top 1.0% of all scored CVEs.
What is the CVSS score of CVE-2017-7668?
CVE-2017-7668 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.2.
How do I remediate CVE-2017-7668?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2017-7668, 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-7668

Explore →

Is Your Infrastructure Affected by CVE-2017-7668?

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

Start Free Scan →Browse All CVEs