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 — 4 sources updated this weekExploited in the wild
9.0EG
EchelonGraph verdictPatch nowTreat as an emergency — this is being exploited.
  • 350 internet-facing services (distinct ip:port) on record running an affected version — derived from Shodan data (© Shodan); a patched service can stay counted while its port stays open
  • 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 services: 350

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.

Internet exposure · derived from Shodan data

350 internet-facing services (distinct ip:port) on record running a version that maps to CVE-2019-0211, in our KEV-Exposure radar’s Shodan-derived sample.

across 54 countries (United States, Germany, France, Japan, United Kingdom)top: http_server
See the KEV-Exposure radar →Derived from Shodan data. Shodan data is owned by Shodan, which holds its copyright (© Shodan). EchelonGraph claims no ownership of it or copyright in it. Aggregate, host-redacted.

How it counts: every 12 hours, when Shodan query credits allow, the radar runs one Shodan query per tracked product, reads up to 100 ip:port services per query, and keeps a service when its banner version matches a CISA-KEV or high-EPSS CVE; a service is dropped when neither a search nor a Shodan InternetDB port re-check has refreshed it for 21 days. A re-check that finds the port still listed by Shodan InternetDB refreshes the service without re-reading the banner, so a patched service can stay counted while its port stays open. A count is a banner-version inference over a sample, not an exploit test and not an internet-wide census, and the unit is a service, not a machine: a machine answering on two ports counts twice.

CVSS v3
7.8
EG Score
9.0CRITICALhigh confidence
EG Risk
81
EG Risk 81/100CISA SSVC

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%
CISA SSVC: Track at low, Attend at medium and Act at high mission impact.
Action: A fix is available. Apply it within your standard update timelines at low, sooner than that at medium and as soon as possible at high mission impact.
EPSS PROB
65%
EPSS %ILE
99th
KEV
⚠ Exploited

CISA SSVCTrack at low, Attend at medium and Act at high mission impact.

A fix is available. Apply it within your standard update timelines at low, sooner than that at medium and as soon as possible at high mission impact.

Exploitation active (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

April 8, 2019

Last Modified

October 27, 2025

Advisory Details (4)

Auto-updated Jun 3, 2026
Patch available.
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 / EcosystemFix (by version range) / PatchReleasedSource
ubuntuapache2-utils (2.4.18-2ubuntu3.10) @ xenial2026-10-05ubuntu
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 rangeFix by version rangeDependents
apache2—
  • every version up to 2.4.39-r0: fixed in 2.4.39-r0
—
Alpine:v3.11(1)
PackageVulnerable rangeFix by version rangeDependents
apache2—
  • every version up to 2.4.39-r0: fixed in 2.4.39-r0
—
Alpine:v3.12(1)
PackageVulnerable rangeFix by version rangeDependents
apache2—
  • every version up to 2.4.39-r0: fixed in 2.4.39-r0
—
Alpine:v3.13(1)
PackageVulnerable rangeFix by version rangeDependents
apache2—
  • every version up to 2.4.39-r0: fixed in 2.4.39-r0
—
Alpine:v3.14(1)
PackageVulnerable rangeFix by version rangeDependents
apache2—
  • every version up to 2.4.39-r0: fixed in 2.4.39-r0
—
Alpine:v3.15(1)
PackageVulnerable rangeFix by version rangeDependents
apache2—
  • every version up to 2.4.39-r0: fixed in 2.4.39-r0
—
Alpine:v3.16(1)
PackageVulnerable rangeFix by version rangeDependents
apache2—
  • every version up to 2.4.39-r0: fixed in 2.4.39-r0
—
Alpine:v3.17(1)
PackageVulnerable rangeFix by version rangeDependents
apache2—
  • every version up to 2.4.39-r0: fixed in 2.4.39-r0
—
Alpine:v3.18(1)
PackageVulnerable rangeFix by version rangeDependents
apache2—
  • every version up to 2.4.39-r0: fixed in 2.4.39-r0
—
Alpine:v3.19(1)
PackageVulnerable rangeFix by version rangeDependents
apache2—
  • every version up to 2.4.39-r0: fixed in 2.4.39-r0
—
Alpine:v3.20(1)
PackageVulnerable rangeFix by version rangeDependents
apache2—
  • every version up to 2.4.39-r0: fixed in 2.4.39-r0
—
Alpine:v3.21(1)
PackageVulnerable rangeFix by version rangeDependents
apache2—
  • every version up to 2.4.39-r0: fixed in 2.4.39-r0
—
Alpine:v3.22(1)
PackageVulnerable rangeFix by version rangeDependents
apache2—
  • every version up to 2.4.39-r0: fixed in 2.4.39-r0
—
Alpine:v3.23(1)
PackageVulnerable rangeFix by version rangeDependents
apache2—
  • every version up to 2.4.39-r0: fixed in 2.4.39-r0
—
Alpine:v3.24(1)
PackageVulnerable rangeFix by version rangeDependents
apache2—
  • every version up to 2.4.39-r0: fixed in 2.4.39-r0
—
Alpine:v3.6(1)
PackageVulnerable rangeFix by version rangeDependents
apache2—
  • every version up to 2.4.39-r0: fixed in 2.4.39-r0
—
Alpine:v3.7(1)
PackageVulnerable rangeFix by version rangeDependents
apache2—
  • every version up to 2.4.39-r0: fixed in 2.4.39-r0
—
Alpine:v3.8(1)
PackageVulnerable rangeFix by version rangeDependents
apache2—
  • every version up to 2.4.39-r0: fixed in 2.4.39-r0
—
Alpine:v3.9(1)
PackageVulnerable rangeFix by version rangeDependents
apache2—
  • every version up to 2.4.39-r0: fixed in 2.4.39-r0
—
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
apache2—
  • every version up to 2.4.38-3: fixed in 2.4.38-3
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
apache2—
  • every version up to 2.4.38-3: fixed in 2.4.38-3
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
apache2—
  • every version up to 2.4.38-3: fixed in 2.4.38-3
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
apache2—
  • every version up to 2.4.38-3: fixed in 2.4.38-3
—
Debian:9(1)
PackageVulnerable rangeFix by version rangeDependents
apache22.4.25-3 ... 2.4.25-3+deb9u6 (7 versions)
  • every version up to 2.4.25-3+deb9u7: fixed in 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 99× in last 7d / 448× 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,837 total refreshes for this CVE.

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

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 product + 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 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 attention. A fix is available. Apply it.
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 (CRITICAL).
Which products are affected by CVE-2019-0211?
CVE-2019-0211 affects Apache HTTP Server. The affected packages EchelonGraph has on record, with version ranges, are listed in the Affected Packages section of this page.
How do I remediate CVE-2019-0211?
A fix for CVE-2019-0211 is available: update to the fixed version the vendor names in its advisory.

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.

Book a Demo →Browse All CVEs