CVE-2019-0211

CRITICALNVD 7.89.0▲
EchelonGraph scoreHIGH confidence

Score elevated to 9.0 because this CVE is listed on the CISA Known Exploited Vulnerabilities catalog (added 2021-11-03), indicating real-world exploitation has been confirmed by US federal agencies. NVD baseline CVSS 7.8 retained for reference. Confidence: HIGH.

Triggered by: CISA KEV (actively exploited)
Sources: cisa_kev, epss, ghsa, nvd
Trending — 5 sources updated this weekExploited in the wild
9.0EG
EchelonGraph verdictPatch nowTreat as an emergency — this is being exploited.
  • 404 internet-exposed hosts are running an affected version right now
  • Actively exploited in the wild (CISA-KEV)
CISA-KEV: ExploitedEPSS PROB: 65%CVSS: 7.8Exploit: cisa kev · ssvc active · epss top5pct · epss high · public exploitExposed: 404

A fix is available — apply it.

In Apache HTTP Server 2.4 releases 2.4.17 to 2.4.38, with MPM event, worker or prefork, code executing in less-privileged child processes or threads (including scripts executed by an in-process scripting interpreter) could execute arbitrary code with the privileges of the parent process (usually root) by manipulating the scoreboard. Non-Unix systems are not affected.

Live · internet exposure

404 internet-exposed hosts are running an affected version of CVE-2019-0211 right now.

across 58 countries (United States, Germany, France, Japan, 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
7.8
EG Score
9.0(high)
EG Risk
81(Attend)
EG Risk 81/100SSVC: Attend

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
Severity90% × 45%
Exploitation100% × 40%
Automatability0% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS PROB
65%
EPSS %ILE
99%
KEV
⚠ Exploited

Published

April 8, 2019

Last Modified

October 27, 2025

Advisory Details (4)

Auto-updated Jun 3, 2026
No patch confirmed yet.
generic
http://www.securityfocus.com/bid/107666
generic

oss-security - Re: Statistics for distros lists updated for 2019Q2

http://www.openwall.com/lists/oss-security/2019/07/26/7
generic

oss-security - CVE-2019-0211: Apache HTTP Server privilege escalation from modules' scripts

http://www.openwall.com/lists/oss-security/2019/04/02/3
generic

Packet Storm

http://packetstormsecurity.com/files/152415/Slackware-Security-Advisory-httpd-Updates.html

Patch Availability(6)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntuapache2-utils (2.4.18-2ubuntu3.10) @ xenial2026-08-21ubuntu
redhathttpd2019-06-18redhat
redhatjbcs-httpd24-openssl-1:1.0.2n-15.jbcs.el72019-05-30redhat
redhatpatch2019-05-30redhat
redhathttpd:2.4-8000020190405071959.55190bc52019-05-07redhat
redhathttpd24-mod_auth_mellon-0:0.13.1-2.el7.12019-04-11redhat

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

(24 across 24 ecosystems)
Alpine:v3.10(1)
PackageVulnerable rangeFixed inDependents
apache2—2.4.39-r0—
Alpine:v3.11(1)
PackageVulnerable rangeFixed inDependents
apache2—2.4.39-r0—
Alpine:v3.12(1)
PackageVulnerable rangeFixed inDependents
apache2—2.4.39-r0—
Alpine:v3.13(1)
PackageVulnerable rangeFixed inDependents
apache2—2.4.39-r0—
Alpine:v3.14(1)
PackageVulnerable rangeFixed inDependents
apache2—2.4.39-r0—
Alpine:v3.15(1)
PackageVulnerable rangeFixed inDependents
apache2—2.4.39-r0—
Alpine:v3.16(1)
PackageVulnerable rangeFixed inDependents
apache2—2.4.39-r0—
Alpine:v3.17(1)
PackageVulnerable rangeFixed inDependents
apache2—2.4.39-r0—
Alpine:v3.18(1)
PackageVulnerable rangeFixed inDependents
apache2—2.4.39-r0—
Alpine:v3.19(1)
PackageVulnerable rangeFixed inDependents
apache2—2.4.39-r0—
Alpine:v3.20(1)
PackageVulnerable rangeFixed inDependents
apache2—2.4.39-r0—
Alpine:v3.21(1)
PackageVulnerable rangeFixed inDependents
apache2—2.4.39-r0—
Alpine:v3.22(1)
PackageVulnerable rangeFixed inDependents
apache2—2.4.39-r0—
Alpine:v3.23(1)
PackageVulnerable rangeFixed inDependents
apache2—2.4.39-r0—
Alpine:v3.24(1)
PackageVulnerable rangeFixed inDependents
apache2—2.4.39-r0—
Alpine:v3.6(1)
PackageVulnerable rangeFixed inDependents
apache2—2.4.39-r0—
Alpine:v3.7(1)
PackageVulnerable rangeFixed inDependents
apache2—2.4.39-r0—
Alpine:v3.8(1)
PackageVulnerable rangeFixed inDependents
apache2—2.4.39-r0—
Alpine:v3.9(1)
PackageVulnerable rangeFixed inDependents
apache2—2.4.39-r0—
Debian:11(1)
PackageVulnerable rangeFixed inDependents
apache2—2.4.38-3—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
apache2—2.4.38-3—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
apache2—2.4.38-3—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
apache2—2.4.38-3—
Debian:9(1)
PackageVulnerable rangeFixed inDependents
apache22.4.25-3 ... 2.4.25-3+deb9u6 (7 versions)2.4.25-3+deb9u7—

Weakness Classification(1)

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 105× in last 7d / 408× 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 1,162 total refreshes for this CVE.

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

Publicly available exploits

(2 references)

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

  • GitHub PoCozkanbilge/Apache-Exploit-2019
    First seen May 12, 2019

    CVE-2019-0211-apache & CVE-2019-6977-imagecolormatch

    Open source ↗
  • Exploit-DBEDB-46676
    First seen Apr 8, 2019

    Apache 2.4.17 < 2.4.38 - 'apache2ctl graceful' 'logrotate' Local Privilege Escalation

    Open source ↗

Related CVEs(same vendor + same CWE)

Frequently asked(6)

What is CVE-2019-0211?
CVE-2019-0211 is a critical vulnerability published on April 8, 2019. In Apache HTTP Server 2.4 releases 2.4.17 to 2.4.38, with MPM event, worker or prefork, code executing in less-privileged child processes or threads (including scripts executed by an in-process scripting interpreter) could execute arbitrary code with the privileges of the parent process (usually…
When was CVE-2019-0211 disclosed?
CVE-2019-0211 was first published in the National Vulnerability Database on April 8, 2019, with the most recent update on October 27, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2019-0211 actively exploited?
Yes. CISA added CVE-2019-0211 to the Known Exploited Vulnerabilities catalog on November 3, 2021, affecting Apache HTTP Server. KEV listing indicates confirmed exploitation in the wild; this CVE warrants immediate patching attention.
What is the CVSS score of CVE-2019-0211?
CVE-2019-0211 has a CVSS v3 base score of 7.8 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 9.0.
Which products are affected by CVE-2019-0211?
CVE-2019-0211 affects Apache HTTP Server. The full affected-products list, including version ranges and fixed versions, is shown in the Affected Packages section of this page.
How do I remediate CVE-2019-0211?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2019-0211, 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-2019-0211

Explore →

Is Your Infrastructure Affected by CVE-2019-0211?

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

Start Free Scan →Browse All CVEs