CVE-2019-10097

HIGHNVD 7.27.9
EchelonGraph scoreHIGH confidence

Score elevated to 7.9 because EPSS predicts 53% probability of exploitation within the next 30 days (top 1.1% of all CVEs). NVD baseline CVSS 7.2 retained for reference. Confidence: see factors.

Triggered by: EPSS exploit prediction ≥85%
Sources: epss, nvd
Trending — 3 sources updated this weekElevated
7.2
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • 98 internet-exposed hosts are running an affected version right now
  • High exploitation likelihood — EPSS 53%
CISA-KEV: Not listedEPSS: 53%CVSS: 7.2Exploit: NoneExposed: 98

A fix is available — apply it.

In Apache HTTP Server 2.4.32-2.4.39, when mod_remoteip was configured to use a trusted intermediary proxy server using the "PROXY" protocol, a specially crafted PROXY header could trigger a stack buffer overflow or NULL pointer deference. This vulnerability could only be triggered by a trusted proxy and not by untrusted HTTP clients.

Live · internet exposure

98 internet-exposed hosts are running an affected version of CVE-2019-10097 right now.

across 27 countries (United States, France, Japan, Germany, United Kingdom)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.2
EG Score
7.9(high)
EG Risk
61(Track)
EG Risk 61/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
Severity79% × 45%
Exploitation53% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
98.9%
KEV
Not listed

Published

September 26, 2019

Last Modified

November 21, 2024

References (34)

Patch Availability(5)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulibapache2-mod-proxy-uwsgi (2.4.38-2ubuntu2.2) @ disco2026-05-27ubuntu
redhathttpd:2.4-8030020200818000036.30b713e62020-11-04redhat
redhathttpd2020-04-06redhat
redhatjbcs-httpd24-openssl-1:1.1.1c-16.jbcs.el72020-04-06redhat
redhathttpd24-nghttp2-0:1.7.1-8.el72019-12-10redhat

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.

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(5)

Data Freshness Timeline

(refreshed 13× in last 7d / 32× 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.

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

Frequently asked(5)

What is CVE-2019-10097?
CVE-2019-10097 is a high vulnerability published on September 26, 2019. In Apache HTTP Server 2.4.32-2.4.39, when mod_remoteip was configured to use a trusted intermediary proxy server using the "PROXY" protocol, a specially crafted PROXY header could trigger a stack buffer overflow or NULL pointer deference. This vulnerability could only be triggered by a trusted…
When was CVE-2019-10097 disclosed?
CVE-2019-10097 was first published in the National Vulnerability Database on September 26, 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-10097 actively exploited?
CVE-2019-10097 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 98.9% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2019-10097?
CVE-2019-10097 has a CVSS v3 base score of 7.2 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 7.9.
How do I remediate CVE-2019-10097?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2019-10097, 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

Explore the affected products and dependency analysis for CVE-2019-10097

Explore →

Is Your Infrastructure Affected by CVE-2019-10097?

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