CVE-2018-1303

HIGHNVD 7.58.6▲
EchelonGraph scoreHIGH confidence

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

A fix is available — apply it.

A specially crafted HTTP request header could have crashed the Apache HTTP Server prior to version 2.4.30 due to an out of bound read while preparing data to be cached in shared memory. It could be used as a Denial of Service attack against users of mod_cache_socache. The vulnerability is considered as low risk since mod_cache_socache is not widely used, mod_cache_disk is not concerned by this vulnerability.

Live · internet exposure

758 internet-exposed hosts are running an affected version of CVE-2018-1303 right now.

across 65 countries (United States, Japan, Germany, Poland, France)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.6(high)
EG Risk
72(Track)
EG Risk 72/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
Severity86% × 45%
Exploitation71% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
70%
EPSS %ILE
99%
KEV
Not listed

Published

March 26, 2018

Last Modified

November 21, 2024

References (50)

Vendor Advisories for CVE-2018-1303(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(6)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntuapache2-utils (2.4.18-2ubuntu3.8) @ xenial2026-05-28ubuntu
ubuntuapache2-utils (2.4.29-1ubuntu4.1) @ bionic2026-05-28ubuntu
redhathttpd-0:2.4.6-95.el72020-09-29redhat
redhatjbcs-httpd24-openssl-1:1.0.2n-14.jbcs.el72019-02-18redhat
redhathttpd2019-02-18redhat
redhathttpd24-nghttp2-0:1.7.1-7.el72018-11-13redhat

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

(27 across 27 ecosystems)
Alpine:v3.10(1)
PackageVulnerable rangeFixed inDependents
apache2—2.4.33-r0—
Alpine:v3.11(1)
PackageVulnerable rangeFixed inDependents
apache2—2.4.33-r0—
Alpine:v3.12(1)
PackageVulnerable rangeFixed inDependents
apache2—2.4.33-r0—
Alpine:v3.13(1)
PackageVulnerable rangeFixed inDependents
apache2—2.4.33-r0—
Alpine:v3.14(1)
PackageVulnerable rangeFixed inDependents
apache2—2.4.33-r0—
Alpine:v3.15(1)
PackageVulnerable rangeFixed inDependents
apache2—2.4.33-r0—
Alpine:v3.16(1)
PackageVulnerable rangeFixed inDependents
apache2—2.4.33-r0—
Alpine:v3.17(1)
PackageVulnerable rangeFixed inDependents
apache2—2.4.33-r0—
Alpine:v3.18(1)
PackageVulnerable rangeFixed inDependents
apache2—2.4.33-r0—
Alpine:v3.19(1)
PackageVulnerable rangeFixed inDependents
apache2—2.4.33-r0—
Alpine:v3.20(1)
PackageVulnerable rangeFixed inDependents
apache2—2.4.33-r0—
Alpine:v3.21(1)
PackageVulnerable rangeFixed inDependents
apache2—2.4.33-r0—
Alpine:v3.22(1)
PackageVulnerable rangeFixed inDependents
apache2—2.4.33-r0—
Alpine:v3.23(1)
PackageVulnerable rangeFixed inDependents
apache2—2.4.33-r0—
Alpine:v3.24(1)
PackageVulnerable rangeFixed inDependents
apache2—2.4.33-r0—
Alpine:v3.4(1)
PackageVulnerable rangeFixed inDependents
apache2—2.4.33-r0—
Alpine:v3.5(1)
PackageVulnerable rangeFixed inDependents
apache2—2.4.33-r0—
Alpine:v3.6(1)
PackageVulnerable rangeFixed inDependents
apache2—2.4.33-r0—
Alpine:v3.7(1)
PackageVulnerable rangeFixed inDependents
apache2—2.4.33-r0—
Alpine:v3.8(1)
PackageVulnerable rangeFixed inDependents
apache2—2.4.33-r0—
Alpine:v3.9(1)
PackageVulnerable rangeFixed inDependents
apache2—2.4.33-r0—
Debian:11(1)
PackageVulnerable rangeFixed inDependents
apache2—2.4.33-1—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
apache2—2.4.33-1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
apache2—2.4.33-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
apache2—2.4.33-1—
Debian:8(1)
PackageVulnerable rangeFixed inDependents
apache22.4.10-10 ... 2.4.10-10+deb8u9 (12 versions)2.4.10-10+deb8u12—
Debian:9(1)
PackageVulnerable rangeFixed inDependents
apache22.4.25-3, 2.4.25-3+deb9u1, 2.4.25-3+deb9u2, 2.4.25-3+deb9u32.4.25-3+deb9u4—

Weakness Classification(1)

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

Additional Vendor Advisories

(5)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

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

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2018-1303?
CVE-2018-1303 is a high vulnerability published on March 26, 2018. A specially crafted HTTP request header could have crashed the Apache HTTP Server prior to version 2.4.30 due to an out of bound read while preparing data to be cached in shared memory. It could be used as a Denial of Service attack against users of modcachesocache. The vulnerability is considered…
When was CVE-2018-1303 disclosed?
CVE-2018-1303 was first published in the National Vulnerability Database on March 26, 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-2018-1303 actively exploited?
CVE-2018-1303 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 70% probability of exploitation in the next 30 days, which ranks it in the top 0.7% of all scored CVEs.
What is the CVSS score of CVE-2018-1303?
CVE-2018-1303 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.6.
How do I remediate CVE-2018-1303?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2018-1303, 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-2018-1303

Explore →

Is Your Infrastructure Affected by CVE-2018-1303?

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

Start Free Scan →Browse All CVEs