CVE-2019-9827

CRITICALNVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 0.8%, top 25% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Elevated
9.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 27%CVSS: 9.8Exploit: NoneExposed: 0

A fix is available — apply it.

Hawt Hawtio through 2.5.0 is vulnerable to SSRF, allowing a remote attacker to trigger an HTTP request from an affected server to an arbitrary host via the initial /proxy/ substring of a URI.

CVSS v3
9.8
EG Score
9.8(medium)
EPSS
97.8%
KEV
Not listed

Published

July 3, 2019

Last Modified

November 21, 2024

References (2)

Vendor Advisories for CVE-2019-9827(3)

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

Patch Availability(3)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatpatch2020-12-08redhat
redhatpatch2020-10-01redhat
redhathawtio2020-09-01redhat

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

(1 across 1 ecosystem)
Maven(1)
PackageVulnerable rangeFixed inDependents
io.hawt:hawtio-core1.1 ... 2.4.0 (123 versions)2.5.0—

Weakness Classification(1)

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

Additional Vendor Advisories

(1)

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2019-9827?
CVE-2019-9827 is a critical vulnerability published on July 3, 2019. Hawt Hawtio through 2.5.0 is vulnerable to SSRF, allowing a remote attacker to trigger an HTTP request from an affected server to an arbitrary host via the initial /proxy/ substring of a URI.
When was CVE-2019-9827 disclosed?
CVE-2019-9827 was first published in the National Vulnerability Database on July 3, 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-9827 actively exploited?
CVE-2019-9827 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 97.8% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2019-9827?
CVE-2019-9827 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2019-9827?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2019-9827, 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-9827

Explore →

Is Your Infrastructure Affected by CVE-2019-9827?

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

Start Free Scan →Browse All CVEs