CVE-2019-0190

HIGHNVD 7.58.3▲
EchelonGraph scoreHIGH confidence

Score elevated to 8.3 because EPSS predicts 60% probability of exploitation within the next 30 days (top 1.0% of all CVEs). NVD baseline CVSS 7.5 retained for reference. Confidence: see factors.

Triggered by: EPSS exploit prediction ≥85%
Sources: epss, ghsa, nvd
Elevated
8.3EG
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • 113 internet-exposed hosts are running an affected version right now
  • High exploitation likelihood — EPSS 59%
CISA-KEV: Not listedEPSS PROB: 59%CVSS: 7.5Exploit: Elevated riskExposed: 113

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

A bug exists in the way mod_ssl handled client renegotiations. A remote attacker could send a carefully crafted request that would cause mod_ssl to enter a loop leading to a denial of service. This bug can be only triggered with Apache HTTP Server version 2.4.37 when using OpenSSL version 1.1.1 or later, due to an interaction in changes to handling of renegotiation attempts.

Live · internet exposure

113 internet-exposed hosts are running an affected version of CVE-2019-0190 right now.

across 29 countries (United States, Japan, Canada, Germany, France)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.5
EG Score
8.3(high)
EG Risk
66(Track)
EG Risk 66/100SSVC: Track

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
Severity83% × 45%
Exploitation60% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
59%
EPSS %ILE
99%
KEV
Not listed

Published

January 30, 2019

Last Modified

November 21, 2024

References (40)

Affected Packages

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

Data Freshness Timeline

(refreshed 6× in last 7d / 25× 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 101 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2019-0190?
CVE-2019-0190 is a high vulnerability published on January 30, 2019. A bug exists in the way modssl handled client renegotiations. A remote attacker could send a carefully crafted request that would cause modssl to enter a loop leading to a denial of service. This bug can be only triggered with Apache HTTP Server version 2.4.37 when using OpenSSL version 1.1.1 or…
When was CVE-2019-0190 disclosed?
CVE-2019-0190 was first published in the National Vulnerability Database on January 30, 2019, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2019-0190 actively exploited?
CVE-2019-0190 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 59% probability of exploitation in the next 30 days, which ranks it in the top 1.0% of all scored CVEs.
What is the CVSS score of CVE-2019-0190?
CVE-2019-0190 has a CVSS v3 base score of 7.5 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 8.3.
How do I remediate CVE-2019-0190?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2019-0190, 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-0190

Explore →

Is Your Infrastructure Affected by CVE-2019-0190?

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

Start Free Scan →Browse All CVEs