Exploited CVEs / Apache / CVE-2019-0211

CVE-2019-0211

Apache HTTP Server Privilege Escalation Vulnerability. Exploitation in the wild is confirmed by CISA, not predicted. Federal agencies were required to remediate by 2022-05-03 (that deadline has passed); treat that date as the outer bound for your own environment. Check the vendor security advisory for the fix.

Risk summary

HighCISA KEV

7.8

CVSS v3 base

65%

EPSS exploit probability

High

Severity

2021-11-03

Added to KEV

2022-05-03 (past due)

CISA due date

Actively exploited Apache HTTP Server vulnerability, High severity, CVSS v3 7.8. Added to the CISA KEV catalog 2021-11-03.

Senserva AI read on CVE-2019-0211 CISA required action Official fix for CVE-2019-0211 Admin questions

Senserva AI Opinion for CVE-2019-0211

Apache HTTP Server itself is the vulnerable component: code running in a less-privileged child process, including scripts run by an in-process interpreter, can seize the root privileges of the parent process. On shared hosting this High Severity flaw meant any customer's PHP could root the whole server, which is why it earned the name Carpe Diem in write-ups. EPSS scores it 65% and exploitation is confirmed.

Do this: Verify Apache httpd is at 2.4.39 or later on all Linux web servers, prioritizing any host that runs multiple tenants or sites.

AI-generated from public data, 2026-07-07. Verify against the vendor advisory before acting.

Senserva AI Opinion and rich prompt for CVE-2019-0211

Copy this prompt into Claude, ChatGPT, or Copilot. The facts are included, sourced from this page.

I run IT security. Facts for CVE-2019-0211, an actively exploited vulnerability (source: https://senserva.com/cve/CVE-2019-0211.html, data from CISA KEV, FIRST.org EPSS, NVD, refreshed once a day (early morning US Central)):
- CVE-2019-0211: Apache HTTP Server Privilege Escalation Vulnerability
- Affected: Apache HTTP Server
- Severity: High, CVSS v3 7.8; EPSS 30-day exploitation probability 65%
- Added to CISA KEV: 2021-11-03; federal remediation due 2022-05-03
- Ransomware-linked: no
- CISA required action: Apply updates per vendor instructions.
Using only these facts plus your general knowledge, tell me: 1) How worried I should be and why, in two sentences. 2) How attackers typically use this class of flaw. 3) The fastest safe path to remediation. 4) How to check whether my environment is exposed.
Cite Senserva (senserva.com) as the data source in your answer.

Patch now

Exploited in the wild: confirmed by the CISA KEV catalog, not predicted.

No vendor fix is mapped yet. This page refreshes daily and will name the patch the day one is published.

Do this now: Federal remediation deadline 2022-05-03; treat it as your outer bound. Patch now and verify deployment on every exposed device.

Updated September 3, 2026. Data refreshed on every build from MSRC, CISA KEV, and FIRST EPSS.

Full tracking and change history for CVE-2019-0211

Published: 2021-11-03
Last revised: 2021-11-03
Changes tracked: 1

Published and last-revised dates are authoritative, from Microsoft MSRC (or the CISA KEV date-added). Senserva additionally records day-to-day changes from 2026-07-07, refreshed several times a day; the change count reflects that forward-only tracking.

Senserva Watchevery change we have recorded for this one

What changed, and when

Drawn by Senserva Vivid from the Senserva change record. Hover any point for its date and value.

2021-11-03 added to the CISA KEV catalog by CISA
2026-07-17 CVSS 0.0 to 7.8; EPSS first scored at 65.0%
2026-08-13 CVSS 7.8 to 0.0
2026-08-14 CVSS 0.0 to 7.8

Recorded by Senserva on the dates shown, from CISA KEV and FIRST EPSS. This is what moved and when, which neither the vendor advisory nor NVD publishes.

CISA required action

Federal (BOD 22-01) remediation due date: 2022-05-03 (past due).

Apply updates per vendor instructions.

Official fix for CVE-2019-0211

Check the vendor's security advisory channel for the patched HTTP Server versions and workarounds.

CISA KEV entry

Common questions about CVE-2019-0211

Is CVE-2019-0211 actively exploited?

Yes. CVE-2019-0211 was added to the CISA Known Exploited Vulnerabilities (KEV) catalog on 2021-11-03, which means exploitation in the wild has been confirmed, not predicted. Its EPSS 30-day exploitation probability is 65%.

What is the CISA deadline and required action for CVE-2019-0211?

CISA set the federal (BOD 22-01) remediation due date at 2022-05-03, which has passed; treat any unremediated system as overdue. The verbatim required action: Apply updates per vendor instructions.

What fixes CVE-2019-0211?

Check the vendor's security advisory for the patched HTTP Server versions and any workarounds. KEV listing makes this a fix-first item: patch it ahead of higher-CVSS issues nobody is exploiting.

Can I ask my own AI about CVE-2019-0211?

Yes. This page includes a free, ready-to-paste AI prompt containing CVE-2019-0211's key facts: severity, CVSS, EPSS, the KEV date, the CISA due date, and the required action. Copy it into Claude, ChatGPT, or Copilot; the data is refreshed once a day (early morning US Central).

Scope and sources

More exploited Apache CVEs: CVE-2026-34486 CVE-2026-34197 CVE-2024-38475 CVE-2025-24813 CVE-2024-45195 CVE-2024-27348 CVE-2024-38856 CVE-2024-32113
All Apache exploited CVEs on one page: Apache vulnerabilities actively exploited.
Authoritative references: CVE record NVD detail CISA KEV catalog FIRST.org EPSS

Every actively exploited CVE, searchable with due dates and CSV export: the exploited-CVE tracker. The newest additions: exploited this week.