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.
CVE-2019-0211
“▲” beside the score: it is higher than NVD's CVSS score.
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. The 9.0 is the floor for confirmed exploitation, not an impact rating: this CVE's impact severity (EG Severity) is CVSS 7.8 HIGH under GitHub Security Advisory CVSS. Confidence: HIGH.
Also known asEUVD-2019-1002 (ENISA EUVD) · GHSA-w9rc-q752-88hf (GitHub Security Advisories)Source: ENISA EUVD
- 90 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) — the reason this is sooner than the SSVC decision on this page at low or medium mission impact
A fix is available — apply it.
90 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.
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
- 75EG Risk 75/100
EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.
How it’s computed (value × EchelonGraph’s weight)Severity78% × 45%Impact severity (EG Severity): CVSS 7.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.Exploitation100% × 40%Fixed at 100% for a CISA KEV listing: EchelonGraph's rule.Automatability0% × 15%CISA's SSVC Automatable value: no (Vulnrichment).SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Attend at medium and Act at high mission impact.Exploitation active (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.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
What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)
The EG score (9.0): severity, escalated by confirmed exploitation. This CVE's 9.0 is the CISA KEV floor for confirmed exploitation, not an impact rating: its impact severity (EG Severity) is CVSS 7.8 HIGH.
- EG Severity
- 7.8 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
- EG Likelihood
- 65% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-01). FIRST's exploitation probability, not an EchelonGraph model.
- Confirmed exploitation
- CISA KEV and EG-KEV Tier 1 (exploited in the wild)Reported apart from the likelihood: an observed fact, not a probability.
- EG Priority
- SSVC Attend at medium mission impactTrack at low, Attend at medium and Act at high mission impact.CISA BOD 26-04: 3 days & forensic triage if the affected system is publicly exposed; 14 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.
SSVC (CISA's decision table, applied by EchelonGraph)Track 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). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table
BOD 26-04 (CISA's remediation timeline, Table 1)3 days & forensic triage if the affected system is publicly exposed; 14 days if it is not.
The score's inputs: In CISA KEV yes (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it
CISA required action“Apply updates per vendor instructions.”
Quoted verbatim from CISA's Known Exploited Vulnerabilities catalog. CISA directs it at US federal civilian executive branch agencies under Binding Operational Directive (BOD) 26-04, which replaced BOD 22-01 on 10 June 2026; it is not EchelonGraph's advice. CISA's notes: https://nvd.nist.gov/vuln/detail/CVE-2019-0211
Published
April 8, 2019
Last Modified
October 27, 2025
Advisory Details (6)
Auto-updated Oct 26, 2026oss-security - Re: Statistics for distros lists updated for 2019Q2
http://www.openwall.com/lists/oss-security/2019/07/26/7oss-security - CVE-2019-0211: Apache HTTP Server privilege escalation from modules' scripts
http://www.openwall.com/lists/oss-security/2019/04/02/3Packet Storm
http://packetstormsecurity.com/files/152441/CARPE-DIEM-Apache-2.4.x-Local-Privilege-Escalation.htmlVendor Advisories for CVE-2019-0211(3)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
- RHSA-2019:1543Red Hat Product SecurityHigh
Red Hat Security Advisory: Red Hat JBoss Core Services Apache HTTP Server 2.4.29 SP2 security update
- RHSA-2019:1297Red Hat Product SecurityHigh
Red Hat Security Advisory: Red Hat JBoss Core Services Apache HTTP Server 2.4.29 SP2 security update
- RHSA-2019:1296Red Hat Product SecurityHigh
Red Hat Security Advisory: Red Hat JBoss Core Services Apache HTTP Server 2.4.29 SP2 security update
Patch Availability(6)
| Vendor / Ecosystem | Fix (by version range) / Patch | Released | Source |
|---|---|---|---|
| ubuntu | apache2-utils (2.4.18-2ubuntu3.10) @ xenial | 2026-10-31 | ubuntu |
| redhat | httpd | 2019-06-18 | redhat |
| redhat | jbcs-httpd24-openssl-1:1.0.2n-15.jbcs.el7 | 2019-05-30 | redhat |
| redhat | patch | 2019-05-30 | redhat |
| redhat | httpd:2.4-8000020190405071959.55190bc5 | 2019-05-07 | redhat |
| redhat | httpd24-mod_auth_mellon-0:0.13.1-2.el7.1 | 2019-04-11 | redhat |
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)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| apache2 | — |
| — |
Alpine:v3.11(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| apache2 | — |
| — |
Alpine:v3.12(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| apache2 | — |
| — |
Alpine:v3.13(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| apache2 | — |
| — |
Alpine:v3.14(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| apache2 | — |
| — |
Alpine:v3.15(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| apache2 | — |
| — |
Alpine:v3.16(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| apache2 | — |
| — |
Alpine:v3.17(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| apache2 | — |
| — |
Alpine:v3.18(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| apache2 | — |
| — |
Alpine:v3.19(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| apache2 | — |
| — |
Alpine:v3.20(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| apache2 | — |
| — |
Alpine:v3.21(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| apache2 | — |
| — |
Alpine:v3.22(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| apache2 | — |
| — |
Alpine:v3.23(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| apache2 | — |
| — |
Alpine:v3.24(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| apache2 | — |
| — |
Alpine:v3.6(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| apache2 | — |
| — |
Alpine:v3.7(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| apache2 | — |
| — |
Alpine:v3.8(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| apache2 | — |
| — |
Alpine:v3.9(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| apache2 | — |
| — |
Debian:11(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| apache2 | — |
| — |
Debian:12(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| apache2 | — |
| — |
Debian:13(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| apache2 | — |
| — |
Debian:14(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| apache2 | — |
| — |
Debian:9(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| apache2 | 2.4.25-3 ... 2.4.25-3+deb9u6 (7 versions) |
| — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Additional Vendor Advisories
(3)
Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.
Data Freshness Timeline
(refreshed 25× in last 7d / 204× in last 30d)
Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.
Showing the most recent 100 of 2,013 refreshes on record for this CVE.
A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 1,913 oldest rows on record are not shown and were not checked, so the counts can still include repeats.
- 2026-11-02 03:20 UTCEG score recompute
- 2026-11-02 03:20 UTCVendor advisory
- 2026-11-02 03:20 UTCGHSA enrichmentGHSA-w9rc-q752-88hf · GitHub severity HIGH · GitHub CVSS 7.8
- 2026-11-01 16:28 UTCEPSS rescoreEPSS 65% · 99th percentile
- 2026-11-01 02:25 UTCEG score recompute
- 2026-11-01 02:25 UTCVendor advisory
- 2026-11-01 02:25 UTCGHSA enrichmentGHSA-w9rc-q752-88hf · GitHub severity HIGH · GitHub CVSS 7.8
- 2026-10-31 01:29 UTCEG score recompute
- 2026-10-31 01:29 UTCVendor advisory
- 2026-10-31 01:29 UTCGHSA enrichmentGHSA-w9rc-q752-88hf · GitHub severity HIGH · GitHub CVSS 7.8
- 2026-10-30 16:28 UTCEPSS rescoreEPSS 65% · 99th percentile
- 2026-10-30 00:34 UTCEG score recompute
- 2026-10-30 00:34 UTCVendor advisory
- 2026-10-30 00:34 UTCGHSA enrichmentGHSA-w9rc-q752-88hf · GitHub severity HIGH · GitHub CVSS 7.8
- 2026-10-28 23:38 UTCEG score recompute
- 2026-10-28 23:38 UTCVendor advisory
- 2026-10-28 23:38 UTCGHSA enrichmentGHSA-w9rc-q752-88hf · GitHub severity HIGH · GitHub CVSS 7.8
- 2026-10-28 16:27 UTCEPSS rescoreEPSS 65% · 99th percentile
- 2026-10-27 22:43 UTCEG score recompute
- 2026-10-27 22:43 UTCVendor advisory
- 2026-10-27 22:42 UTCGHSA enrichmentGHSA-w9rc-q752-88hf · GitHub severity HIGH · GitHub CVSS 7.8
- 2026-10-27 16:27 UTCEPSS rescoreEPSS 65% · 99th percentile
- 2026-10-26 21:45 UTCEG score recompute
- 2026-10-26 21:45 UTCVendor advisory
- 2026-10-26 21:45 UTCGHSA enrichmentGHSA-w9rc-q752-88hf · GitHub severity HIGH · GitHub CVSS 7.8
Show 75 moreShow fewer
- 2026-10-26 16:27 UTCEPSS rescoreEPSS 65% · 99th percentile
- 2026-10-25 20:47 UTCVendor advisory
- 2026-10-25 20:47 UTCGHSA enrichmentGHSA-w9rc-q752-88hf · GitHub severity HIGH · GitHub CVSS 7.8
- 2026-10-25 19:13 UTCEG score recompute
- 2026-10-25 16:27 UTCEPSS rescoreEPSS 65% · 99th percentile
- 2026-10-24 19:51 UTCEG score recompute
- 2026-10-24 19:51 UTCVendor advisory
- 2026-10-24 19:51 UTCGHSA enrichmentGHSA-w9rc-q752-88hf · GitHub severity HIGH · GitHub CVSS 7.8
- 2026-10-23 18:56 UTCEG score recompute
- 2026-10-23 18:56 UTCVendor advisory
- 2026-10-23 18:56 UTCGHSA enrichmentGHSA-w9rc-q752-88hf · GitHub severity HIGH · GitHub CVSS 7.8
- 2026-10-23 16:27 UTCEPSS rescoreEPSS 65% · 99th percentile
- 2026-10-22 18:00 UTCEG score recompute
- 2026-10-22 18:00 UTCVendor advisory
- 2026-10-22 17:59 UTCGHSA enrichmentGHSA-w9rc-q752-88hf · GitHub severity HIGH · GitHub CVSS 7.8
- 2026-10-21 17:04 UTCEG score recompute
- 2026-10-21 17:04 UTCVendor advisory
- 2026-10-21 17:04 UTCGHSA enrichmentGHSA-w9rc-q752-88hf · GitHub severity HIGH · GitHub CVSS 7.8
- 2026-10-21 16:27 UTCEPSS rescoreEPSS 65% · 99th percentile
- 2026-10-20 16:27 UTCEPSS rescoreEPSS 65% · 99th percentile
- 2026-10-20 16:09 UTCEG score recompute
- 2026-10-20 16:09 UTCVendor advisory
- 2026-10-20 16:08 UTCGHSA enrichmentGHSA-w9rc-q752-88hf · GitHub severity HIGH · GitHub CVSS 7.8
- 2026-10-19 16:27 UTCEPSS rescoreEPSS 65% · 99th percentile
- 2026-10-19 15:07 UTCEG score recompute
- 2026-10-19 15:07 UTCVendor advisory
- 2026-10-19 15:07 UTCGHSA enrichmentGHSA-w9rc-q752-88hf · GitHub severity HIGH · GitHub CVSS 7.8
- 2026-10-18 14:12 UTCVendor advisory
- 2026-10-18 14:12 UTCGHSA enrichmentGHSA-w9rc-q752-88hf · GitHub severity HIGH · GitHub CVSS 7.8
- 2026-10-18 09:59 UTCEG score recompute
- 2026-10-17 13:17 UTCEG score recompute
- 2026-10-17 13:17 UTCVendor advisory
- 2026-10-17 13:17 UTCGHSA enrichmentGHSA-w9rc-q752-88hf · GitHub severity HIGH · GitHub CVSS 7.8
- 2026-10-16 16:30 UTCEPSS rescoreEPSS 65% · 99th percentile
- 2026-10-16 12:21 UTCEG score recompute
- 2026-10-16 12:21 UTCVendor advisory
- 2026-10-16 12:21 UTCGHSA enrichmentGHSA-w9rc-q752-88hf · GitHub severity HIGH · GitHub CVSS 7.8
- 2026-10-15 11:25 UTCEG score recompute
- 2026-10-15 11:25 UTCVendor advisory
- 2026-10-15 11:25 UTCGHSA enrichmentGHSA-w9rc-q752-88hf · GitHub severity HIGH · GitHub CVSS 7.8
- 2026-10-14 16:27 UTCEPSS rescoreEPSS 65% · 99th percentile
- 2026-10-14 10:30 UTCEG score recompute
- 2026-10-14 10:30 UTCVendor advisory
- 2026-10-14 10:29 UTCGHSA enrichmentGHSA-w9rc-q752-88hf · GitHub severity HIGH · GitHub CVSS 7.8
- 2026-10-13 16:27 UTCEPSS rescoreEPSS 65% · 99th percentile
- 2026-10-13 09:33 UTCVendor advisory
- 2026-10-13 09:33 UTCGHSA enrichmentGHSA-w9rc-q752-88hf · GitHub severity HIGH · GitHub CVSS 7.8
- 2026-10-12 20:06 UTCEG score recompute
- 2026-10-12 16:28 UTCEPSS rescoreEPSS 65% · 99th percentile
- 2026-10-12 08:36 UTCVendor advisory
- 2026-10-12 08:35 UTCGHSA enrichmentGHSA-w9rc-q752-88hf · GitHub severity HIGH · GitHub CVSS 7.8
- 2026-10-12 04:54 UTCVendor advisory
- 2026-10-12 04:54 UTCGHSA enrichmentGHSA-w9rc-q752-88hf · GitHub severity HIGH · GitHub CVSS 7.8
- 2026-10-12 01:14 UTCVendor advisory
- 2026-10-12 01:14 UTCGHSA enrichmentGHSA-w9rc-q752-88hf · GitHub severity HIGH · GitHub CVSS 7.8
- 2026-10-11 21:35 UTCEG score recompute
- 2026-10-11 21:35 UTCVendor advisory
- 2026-10-11 21:35 UTCGHSA enrichmentGHSA-w9rc-q752-88hf · GitHub severity HIGH · GitHub CVSS 7.8
- 2026-10-11 17:56 UTCEG score recompute
- 2026-10-11 17:56 UTCVendor advisory
- 2026-10-11 17:55 UTCGHSA enrichmentGHSA-w9rc-q752-88hf · GitHub severity HIGH · GitHub CVSS 7.8
- 2026-10-11 14:14 UTCEG score recompute
- 2026-10-11 14:14 UTCVendor advisory
- 2026-10-11 14:14 UTCGHSA enrichmentGHSA-w9rc-q752-88hf · GitHub severity HIGH · GitHub CVSS 7.8
- 2026-10-11 13:41 UTCEPSS rescoreEPSS 65% · 99th percentile
- 2026-10-11 10:35 UTCVendor advisory
- 2026-10-11 10:35 UTCGHSA enrichmentGHSA-w9rc-q752-88hf · GitHub severity HIGH · GitHub CVSS 7.8
- 2026-10-11 06:55 UTCVendor advisory
- 2026-10-11 06:55 UTCGHSA enrichmentGHSA-w9rc-q752-88hf · GitHub severity HIGH · GitHub CVSS 7.8
- 2026-10-11 03:15 UTCVendor advisory
- 2026-10-11 03:15 UTCGHSA enrichmentGHSA-w9rc-q752-88hf · GitHub severity HIGH · GitHub CVSS 7.8
- 2026-10-10 23:35 UTCEG score recompute
- 2026-10-10 23:35 UTCVendor advisory
- 2026-10-10 23:34 UTCGHSA enrichmentGHSA-w9rc-q752-88hf · GitHub severity HIGH · GitHub CVSS 7.8
- 2026-10-10 19:55 UTCEPSS rescoreEPSS 65% · 99th percentile
Publicly available exploits
(2 references)Public exploit code is referenced for this CVE (1 Exploit-DB entry, 1 GitHub PoC). Defenders should treat patch urgency accordingly.
- GitHub PoCozkanbilge/Apache-Exploit-2019Published May 12, 2019
CVE-2019-0211-apache & CVE-2019-6977-imagecolormatch
Open source ↗ - Exploit-DBEDB-46676Published 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)· as of November 1, 2026
Same product
10 shownAlpine:v3.6:apache2
- CVE-2018-1312EG 9.8EPSS p97CRITICAL
- CVE-2017-7679EG 9.8EPSS p99CRITICAL
- CVE-2017-3169EG 9.8EPSS p97CRITICAL
- CVE-2017-3167EG 9.8EPSS p97CRITICAL
- CVE-2017-15715NVD 8.1EG 9.0EPSS p100CRITICAL
- CVE-2017-9798NVD 7.5EG 9.0EPSS p100CRITICAL
- CVE-2018-1303NVD 7.5EG 8.6EPSS p99HIGH
- CVE-2017-7668NVD 7.5EG 8.2EPSS p99HIGH
- CVE-2019-0217EG 7.5EPSS p97HIGH
- CVE-2018-17199EG 7.5EPSS p97HIGH
Same vendor
10 shownredhat:RHSA-2019:1296 · redhat:RHSA-2019:1543
- CVE-2018-0732NVD 7.5EG 8.0EPSS p99HIGH
- CVE-2018-0495EG 4.7MEDIUM
- CVE-2019-3822EG 9.8EPSS p96CRITICAL
- CVE-2018-16840EG 9.8CRITICAL
- CVE-2018-16839NVD 4.3EG 9.8EPSS p93CRITICAL
- CVE-2018-1000120EG 9.8EPSS p96CRITICAL
- CVE-2018-1000007EG 9.8EPSS p96CRITICAL
- CVE-2018-16842NVD 4.4EG 9.1CRITICAL
- CVE-2018-1000122EG 9.1EPSS p95CRITICAL
- CVE-2018-1000005EG 9.1EPSS p92CRITICAL
Same CWE
10 shownCWE-416
Frequently asked(6)
What is CVE-2019-0211?
When was CVE-2019-0211 made public?
Is CVE-2019-0211 actively exploited?
What is the CVSS score of CVE-2019-0211?
Which products are affected by CVE-2019-0211?
How do I remediate CVE-2019-0211?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2019-0211
Is Your Infrastructure Affected by CVE-2019-0211?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.