CVE-2019-10092

HIGHNVD 6.18.8▲
EchelonGraph scoreHIGH confidence

Score elevated to 8.8 because EPSS predicts 81% probability of exploitation within the next 30 days (top 0.4% of all CVEs). NVD baseline CVSS 6.1 retained for reference. Confidence: see factors.

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

A fix is available — apply it.

In Apache HTTP Server 2.4.0-2.4.39, a limited cross-site scripting issue was reported affecting the mod_proxy error page. An attacker could cause the link on the error page to be malformed and instead point to a page of their choice. This would only be exploitable where a server was set up with proxying enabled but was misconfigured in such a way that the Proxy Error page was displayed.

Live · internet exposure

676 internet-exposed hosts are running an affected version of CVE-2019-10092 right now.

across 68 countries (United States, Germany, Japan, France, Canada)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
6.1
EG Score
8.8(high)
EG Risk
77(Track)
EG Risk 77/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
Severity88% × 45%
Exploitation81% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
81%
EPSS %ILE
100%
KEV
Not listed

Published

September 26, 2019

Last Modified

November 21, 2024

References (68)

Vendor Advisories for CVE-2019-10092(3)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(5)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntuapache2-utils (2.4.18-2ubuntu3.12) @ xenial2026-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.

Affected Packages

(25 across 25 ecosystems)
Alpine:v3.10(1)
PackageVulnerable rangeFixed inDependents
apache2—2.4.41-r0—
Alpine:v3.11(1)
PackageVulnerable rangeFixed inDependents
apache2—2.4.41-r0—
Alpine:v3.12(1)
PackageVulnerable rangeFixed inDependents
apache2—2.4.41-r0—
Alpine:v3.13(1)
PackageVulnerable rangeFixed inDependents
apache2—2.4.41-r0—
Alpine:v3.14(1)
PackageVulnerable rangeFixed inDependents
apache2—2.4.41-r0—
Alpine:v3.15(1)
PackageVulnerable rangeFixed inDependents
apache2—2.4.41-r0—
Alpine:v3.16(1)
PackageVulnerable rangeFixed inDependents
apache2—2.4.41-r0—
Alpine:v3.17(1)
PackageVulnerable rangeFixed inDependents
apache2—2.4.41-r0—
Alpine:v3.18(1)
PackageVulnerable rangeFixed inDependents
apache2—2.4.41-r0—
Alpine:v3.19(1)
PackageVulnerable rangeFixed inDependents
apache2—2.4.41-r0—
Alpine:v3.20(1)
PackageVulnerable rangeFixed inDependents
apache2—2.4.41-r0—
Alpine:v3.21(1)
PackageVulnerable rangeFixed inDependents
apache2—2.4.41-r0—
Alpine:v3.22(1)
PackageVulnerable rangeFixed inDependents
apache2—2.4.41-r0—
Alpine:v3.23(1)
PackageVulnerable rangeFixed inDependents
apache2—2.4.41-r0—
Alpine:v3.24(1)
PackageVulnerable rangeFixed inDependents
apache2—2.4.41-r0—
Alpine:v3.7(1)
PackageVulnerable rangeFixed inDependents
apache2—2.4.41-r0—
Alpine:v3.8(1)
PackageVulnerable rangeFixed inDependents
apache2—2.4.41-r0—
Alpine:v3.9(1)
PackageVulnerable rangeFixed inDependents
apache2—2.4.41-r0—
Debian:10(1)
PackageVulnerable rangeFixed inDependents
apache22.4.38-3, 2.4.38-3+deb10u1, 2.4.38-3+deb10u22.4.38-3+deb10u3—
Debian:11(1)
PackageVulnerable rangeFixed inDependents
apache2—2.4.41-1—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
apache2—2.4.41-1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
apache2—2.4.41-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
apache2—2.4.41-1—
Debian:8(1)
PackageVulnerable rangeFixed inDependents
apache22.4.10-10 ... 2.4.10-10+deb8u9 (15 versions)2.4.10-10+deb8u15—
Debian:9(1)
PackageVulnerable rangeFixed inDependents
apache22.4.25-3 ... 2.4.25-3+deb9u8 (9 versions)2.4.25-3+deb9u9—

Weakness Classification(1)

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

Additional Vendor Advisories

(2)

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 5× in last 7d / 16× 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-08-21 14:44 UTCOSV refresh
  2. 2026-08-20 22:51 UTCEPSS rescore
  3. 2026-08-19 17:00 UTCEPSS rescore
  4. 2026-08-17 13:43 UTCEPSS rescore
  5. 2026-08-16 02:10 UTCEPSS rescore
  6. 2026-08-13 21:56 UTCEPSS rescore
  7. 2026-08-12 13:47 UTCEPSS rescore
  8. 2026-08-06 00:51 UTCOSV refresh
  9. 2026-08-05 19:13 UTCEPSS rescore
  10. 2026-07-28 15:32 UTCEPSS rescore
  11. 2026-07-26 14:51 UTCEPSS rescore
  12. 2026-07-24 14:14 UTCEPSS rescore
  13. 2026-07-24 14:14 UTCEPSS rescore
  14. 2026-07-23 14:15 UTCEPSS rescore
  15. 2026-07-23 01:38 UTCEG score recompute▲ 2.70
  16. 2026-07-22 22:18 UTCEG score recompute
  17. 2026-07-22 14:05 UTCEPSS rescore
  18. 2026-07-21 15:22 UTCEPSS rescore
  19. 2026-07-21 15:22 UTCEPSS rescore
  20. 2026-07-20 17:04 UTCEPSS rescore
  21. 2026-07-20 05:16 UTCOSV refresh
  22. 2026-07-19 02:26 UTCEPSS rescore
  23. 2026-07-19 02:26 UTCEPSS rescore
  24. 2026-07-15 16:55 UTCEPSS rescore
  25. 2026-07-12 05:43 UTCEPSS rescore
Show 38 more
  1. 2026-07-09 19:06 UTCEPSS rescore
  2. 2026-07-07 13:42 UTCEPSS rescore
  3. 2026-07-06 16:25 UTCEPSS rescore
  4. 2026-07-05 02:27 UTCEPSS rescore
  5. 2026-07-02 21:35 UTCOSV refresh
  6. 2026-07-02 16:56 UTCEPSS rescore
  7. 2026-06-30 23:20 UTCEPSS rescore
  8. 2026-06-30 23:20 UTCEPSS rescore
  9. 2026-06-25 13:47 UTCEPSS rescore
  10. 2026-06-25 13:47 UTCEPSS rescore
  11. 2026-06-23 21:30 UTCEPSS rescore
  12. 2026-06-23 21:30 UTCEPSS rescore
  13. 2026-06-21 01:57 UTCEPSS rescore
  14. 2026-06-21 01:57 UTCEPSS rescore
  15. 2026-06-17 17:50 UTCEPSS rescore
  16. 2026-06-15 17:45 UTCEPSS rescore
  17. 2026-06-14 17:43 UTCOSV refresh
  18. 2026-06-13 22:58 UTCEPSS rescore
  19. 2026-06-12 23:09 UTCEPSS rescore
  20. 2026-06-10 22:16 UTCEPSS rescore
  21. 2026-06-08 14:15 UTCEPSS rescore
  22. 2026-06-08 14:14 UTCEPSS rescore
  23. 2026-06-06 13:45 UTCEPSS rescore
  24. 2026-06-06 13:45 UTCEPSS rescore
  25. 2026-06-05 22:45 UTCEPSS rescore
  26. 2026-06-05 22:45 UTCEPSS rescore
  27. 2026-06-05 06:08 UTCEPSS rescore
  28. 2026-06-05 06:08 UTCEPSS rescore
  29. 2026-05-31 00:14 UTCEPSS rescore
  30. 2026-05-31 00:14 UTCEPSS rescore
  31. 2026-05-29 13:42 UTCEPSS rescore
  32. 2026-05-27 13:53 UTCEG score recompute
  33. 2026-05-27 13:53 UTCVendor advisory
  34. 2026-05-27 13:53 UTCGHSA enrichment
  35. 2026-05-27 13:38 UTCEPSS rescore
  36. 2026-05-26 07:17 UTCEPSS rescore
  37. 2026-05-26 07:17 UTCEPSS rescore
  38. 2026-05-24 23:43 UTCOSV refresh

Publicly available exploits

(3 references)

Working exploit code is in the public domain (1 GitHub PoC) (1 Exploit-DB entry). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • GitHub PoCmotikan2010/CVE-2019-10092_Docker
    First seen Dec 18, 2019

    CVE-2019-10092 Docker - Apache HTTP Server

    Open source ↗
  • Exploit-DBEDB-47688
    First seen Oct 14, 2019

    Apache Httpd mod_proxy - Error Page Cross-Site Scripting

    Open source ↗
  • Nucleihttp/cves/2019/CVE-2019-10092.yaml
    First seen Jan 1, 2019

    Apache HTTP Server <=2.4.39 - HTML Injection/Partial Cross-Site Scripting

    Open source ↗

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2019-10092?
CVE-2019-10092 is a high vulnerability published on September 26, 2019. In Apache HTTP Server 2.4.0-2.4.39, a limited cross-site scripting issue was reported affecting the mod_proxy error page. An attacker could cause the link on the error page to be malformed and instead point to a page of their choice. This would only be exploitable where a server was set up with…
When was CVE-2019-10092 disclosed?
CVE-2019-10092 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-10092 actively exploited?
CVE-2019-10092 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 81% probability of exploitation in the next 30 days, which ranks it in the top 0.4% of all scored CVEs.
What is the CVSS score of CVE-2019-10092?
CVE-2019-10092 has a CVSS v3 base score of 6.1 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 8.8.
How do I remediate CVE-2019-10092?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2019-10092, 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-10092

Explore →

Is Your Infrastructure Affected by CVE-2019-10092?

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

Start Free Scan →Browse All CVEs