How severe is CVE-2019-0211?

CVE-2019-0211 has a CVSS score of 7.8/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2019-0211?

Affected package information for CVE-2019-0211 is not yet fully mapped. Check the official advisory links for details.

How do I fix CVE-2019-0211?

No fixed release is recorded for CVE-2019-0211 yet. Track the upstream advisory, and apply the exposure-reduction steps below in the meantime.

How do I detect CVE-2019-0211 in my code and dependencies?

Identify every host running the affected component and compare the installed build against the fixed version below — for source-built or distro-packaged software the version string, not a lockfile, is the source of truth (`dpkg -l`, `rpm -q`, or the binary's own `--version`).

How do I mitigate CVE-2019-0211 if there is no patch (or I can't update yet)?

Constrain what reaches the vulnerable code: limit the size and shape of untrusted input, isolate the affected component in a sandboxed or least-privileged process, and enable the platform's memory-safety mitigations (ASLR, stack protector, hardened allocator) so an out-of-bounds access is more likely to fail closed than to be exploitable.

Is CVE-2019-0211 actively exploited in the wild?

Yes. There are 9 known exploit references for CVE-2019-0211, including 1 documented proof-of-concept exploit on Exploit-DB and 6 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2019-0211?

CVE-2019-0211 has an EPSS (Exploit Prediction Scoring System) score of 65.0%, placing it in the 99th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

Is CVE-2019-0211 in the CISA Known Exploited Vulnerabilities catalog?

Yes. CVE-2019-0211 (Apache HTTP Server Privilege Escalation Vulnerability) was added to CISA's Known Exploited Vulnerabilities (KEV) catalog on 2021-11-03. CISA required all US federal civilian agencies to remediate this vulnerability by 2022-05-03. The required action was: Apply updates per vendor instructions. Being listed in the KEV catalog is the strongest possible confirmation of active exploitation — treat this as a critical priority.

What type of vulnerability is CVE-2019-0211?

CVE-2019-0211 is classified as Use After Free (CWE-416). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2019-0211 published, and has it been updated?

CVE-2019-0211 was published on April 8, 2019 and was last updated on October 24, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🛡️

CISA KEV · ACTIVELY EXPLOITED

HIGH severity

CVE-2019-0211 — httpd

HIGH

CVE-2019-0211 is a high-severity (CVSS 7.8) Use After Free vulnerability. It is in CISA's Known Exploited Vulnerabilities catalog (added 2021-11-03) — treat it as actively exploited and patch now. No vendor fix is recorded yet; mitigation options are listed below.

Published

Apr 8, 2019

Updated

Oct 24, 2026

Affected

27 products

Patched

See advisory

Exploits

9 known

Exploitation data as of Oct 22, 2026 · OSV.dev, NVD, CISA KEV, FIRST.org (EPSS)

Exploitation Status

Actively exploited in the wild

Confirmed by CISA's Known Exploited Vulnerabilities catalog on 2021-11-03. Federal agencies were required to remediate by 2022-05-03.
A successful exploit gives an attacker total control of the affected component, not partial access.

Exploitation and automatability from CISA (KEV catalog and SSVC triage) for CVE-2019-0211.

EPSS Exploitation Probability

via FIRST.org ↗

65.0%probability of exploitation in next 30 days

High Risk0.00%

Lower risk than most CVEs99th percentile — riskier than 99% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

CVE-2019-0211 by exploitation likelihood (EPSS) against impact (CVSS). In the shaded patch-first corner (EPSS 50%+, CVSS 7.0+).

Where this sits among everything scored

Of 395,249 CVEs with a current EPSS score, this one falls in the 50–90% band (highlighted). Counts from FIRST.org, log-scaled.

Description

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.

Affected Products

27 products · 68 configurations

Application

http serverapache

≥ 2.4.17 && ≤ 2.4.38

range

ubuntu linuxcanonical

4 versions

14.0416.0418.0418.10

debian linuxdebian

1 version

9.0

fedorafedoraproject

3 versions

282930

Application

oncommand unified managernetapp

all

leapopensuse

2 versions

15.042.3

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

EDB-46676locallinux

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

by cfreal · Apr 8, 2019

Exploit-DB Source

Detection & mitigation playbook

Vulnerability

Detect
Identify every host running the affected component and compare the installed build against the fixed version below — for source-built or distro-packaged software the version string, not a lockfile, is the source of truth (`dpkg -l`, `rpm -q`, or the binary's own `--version`).
Remediation status
No fixed release is recorded for CVE-2019-0211 yet. Track the upstream advisory, and apply the exposure-reduction steps below in the meantime.
Mitigate without a patch
Constrain what reaches the vulnerable code: limit the size and shape of untrusted input, isolate the affected component in a sandboxed or least-privileged process, and enable the platform's memory-safety mitigations (ASLR, stack protector, hardened allocator) so an out-of-bounds access is more likely to fail closed than to be exploitable.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatImportant

This flaw is exploitable in httpd if it is configured to allow an untrusted user to upload and execute arbitrary scripts. Due to the nature of the flaw, the uploaded script would not run as a restricted privileged user, but rather it runs as root allowing for privilege escalation from the restricted user to root on…

Product	Fixed in	Advisory
JBoss Core Services Apache HTTP Server 2.4.29 SP2	see advisory	RHSA-2019:1296
JBoss Core Services Apache HTTP Server 2.4.29 SP2	`httpd`	RHSA-2019:1543
JBoss Core Services on RHEL 6	`jbcs-httpd24-httpd-0:2.4.29-40.jbcs.el6`	RHSA-2019:1297
Red Hat Enterprise Linux 8	`httpd:2.4-8000020190405071959.55190bc5`	RHSA-2019:0980
Red Hat Software Collections for Red Hat Enterprise Linux 6	`httpd24-httpd-0:2.4.34-7.el6.1`	RHSA-2019:0746

UbuntuHIGH

USN-3937-1Ubuntu

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2019-0211 in your dependencies?

Find it across , including transitive dependencies.

Scan my dependencies How O3 SCA works