CVE-2014-0226

NONECVSS 0.0Trending — 5 sources updated this weekElevated
0.0
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • 200 internet-exposed hosts are running an affected version right now
  • High exploitation likelihood — EPSS 86%
CISA-KEV: Not listedEPSS: 86%CVSS: —Exploit: NoneExposed: 200

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

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

across 40 countries (United States, Japan, United Kingdom, Italy, Canada)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
—
EG Score
0.0(none)
EG Risk
0
EG Risk 0/100

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. It is distinct from the 0–10 EG Score, which measures severity.

EPSS
99.7%
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.

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

Related CVEs(same vendor + same CWE)

Frequently asked(4)

What is CVE-2014-0226?
CVE-2014-0226 is a none 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 99.7% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
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

Explore the affected products and dependency analysis for 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