CVE-2014-0226

MEDIUMCVSS v2 · 6.86.8—
EchelonGraph scoreLOW confidence

This CVE was only ever scored under CVSS v2.0. NVD CVSS v2.0 base 6.8 — v2 rates that MEDIUM (v2 bands: LOW 0.0–3.9 / MEDIUM 4.0–6.9 / HIGH 7.0–10.0; v2 has no CRITICAL band). Vector AV:N/AC:M/Au:N/C:P/I:P/A:P. CVSS v2 is an older, coarser metric than v3.1/v4.0 (no Scope, no User Interaction, no Attack Requirements), so it is not directly comparable to a v3 or v4 score. NVD has never re-scored this record under v3. EPSS predicts 85.7% exploitation probability in the next 30 days, which is reflected in EG Risk but does not lift the v2 base. Confidence: LOW.

Sources: epss, nvd_v2
Elevated
6.8EG
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • 303 internet-exposed hosts are running an affected version right now
  • High exploitation likelihood — EPSS 86%
CISA-KEV: Not listedEPSS PROB: 86%CVSS v2: 6.8Exploit: Elevated riskExposed: 303

A fix is available — apply it.

Race condition in the mod_status module in the Apache HTTP Server before 2.4.10 allows remote attackers to cause a denial of service (heap-based buffer overflow), or possibly obtain sensitive credential information or execute arbitrary code, via a crafted request that triggers improper scoreboard handling within the status_handler function in modules/generators/mod_status.c and the lua_ap_scoreboard_worker function in modules/lua/lua_request.c.

Live · internet exposure

303 internet-exposed hosts are running an affected version of CVE-2014-0226 right now.

across 47 countries (United States, Japan, Italy, Germany, 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 v2.0 (legacy)
6.8MEDIUMNVD never assigned a CVSS v3 rating to this CVE
EG Score
6.8(low)
EG Risk
69(Track)
EG Risk 69/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
Severity68% × 45%
Exploitation86% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
86%
EPSS %ILE
100%
KEV
Not listed

Published

July 20, 2014

Last Modified

May 6, 2026

References (106)

Patch Availability(10)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulibapache2-mod-proxy-html (1:2.4.7-1ubuntu4.1) @ trusty2026-05-28ubuntu
redhattomcat-native-0:1.1.30-2.redhat_1.ep6.el62014-08-21redhat
redhatpatch2014-08-21redhat
redhattomcat-native-0:1.1.30-2.redhat_1.ep6.el52014-08-21redhat
redhatxom-0:1.2.7-3.redhat_4.1.ep6.el52014-08-06redhat
redhatxom-0:1.2.7-3.redhat_4.1.ep6.el62014-08-06redhat
redhatpatch2014-08-06redhat
redhathttpd24-httpd-0:2.4.6-21.el72014-07-23redhat
redhathttpd-0:2.2.15-31.el6_52014-07-23redhat
redhathttpd-0:2.4.6-18.el7_02014-07-23redhat

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

(6 across 6 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
apache2—2.4.10-1—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
apache2—2.4.10-1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
apache2—2.4.10-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
apache2—2.4.10-1—
Debian:6.0(1)
PackageVulnerable rangeFixed inDependents
apache22.2.16-6 ... 2.2.16-6+squeeze8 (14 versions)2.2.16-6+squeeze13—
Debian:7(1)
PackageVulnerable rangeFixed inDependents
apache22.2.22-13, 2.2.22-13+deb7u1, 2.2.22-13+deb7u22.2.22-13+deb7u3—

Weakness Classification(1)

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

All Vendor Advisories

(10)

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

Publicly available exploits

(1 reference)

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-34133
    First seen Jul 21, 2014

    Apache 2.4.7 mod_status - Scoreboard Handling Race Condition

    Open source ↗

Frequently asked(4)

What is CVE-2014-0226?
CVE-2014-0226 is a medium vulnerability published on July 20, 2014. Race condition in the modstatus module in the Apache HTTP Server before 2.4.10 allows remote attackers to cause a denial of service (heap-based buffer overflow), or possibly obtain sensitive credential information or execute arbitrary code, via a crafted request that triggers improper scoreboard…
When was CVE-2014-0226 disclosed?
CVE-2014-0226 was first published in the National Vulnerability Database on July 20, 2014, with the most recent update on May 6, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2014-0226 actively exploited?
CVE-2014-0226 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 86% probability of exploitation in the next 30 days, which ranks it in the top 0.3% of all scored CVEs.
How do I remediate CVE-2014-0226?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2014-0226, 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-2014-0226

Explore →

Is Your Infrastructure Affected by CVE-2014-0226?

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

Start Free Scan →Browse All CVEs