CVE-2018-9160

CRITICALNVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 76.5%, top 1% 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
Trending — 3 sources updated this weekWeaponized
9.8
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 77%
CISA-KEV: Not listedEPSS: 77%CVSS: 9.8Exploit: NoneExposed: 0

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

SickRage before v2018.03.09-1 includes cleartext credentials in HTTP responses.

CVSS v3
9.8
EG Score
9.8(medium)
EG Risk
79(Track*)
EG Risk 79/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
Severity98% × 45%
Exploitation77% × 40%
Automatability30% × 15%
Action: Watch closely — could escalate to Attend.
EPSS
99.5%
KEV
Not listed

Published

March 31, 2018

Last Modified

November 21, 2024

Advisory Details (2)

Auto-updated Jun 28, 2026
🔬 Proof of concept available. Upstream fix merged — awaiting tagged release. Sources: github_commit.
generic🟡 PoC Available

SickRage < v2018.03.09 - Clear-Text Credentials HTTP Response - Linux webapps Exploit

https://www.exploit-db.com/exploits/44545/
github_commit

commit 8156a74a68ae (SickRage/SickRage)

Fix landed in SickRage/SickRage commit 8156a74a68ae — awaiting tagged release

https://github.com/SickRage/SickRage/commit/8156a74a68aea930d1e1047baba8b115c3abfc44

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFixed inDependents
sickrage6.0.47 ... 9.2.99 (314 versions)9.3.2—

Weakness Classification(1)

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

Data Freshness Timeline

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

Publicly available exploits

(2 references)

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

  • Exploit-DBEDB-44545
    First seen Apr 26, 2018

    SickRage < v2018.03.09 - Clear-Text Credentials HTTP Response

    Open source ↗
  • Metasploitauxiliary/scanner/http/http_sickrage_password_leak✓ verified
    First seen Mar 8, 2018

    HTTP SickRage Password Leak

    Open source ↗

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2018-9160?
CVE-2018-9160 is a critical vulnerability published on March 31, 2018. SickRage before v2018.03.09-1 includes cleartext credentials in HTTP responses.
When was CVE-2018-9160 disclosed?
CVE-2018-9160 was first published in the National Vulnerability Database on March 31, 2018, 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-2018-9160 actively exploited?
CVE-2018-9160 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 99.5% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2018-9160?
CVE-2018-9160 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2018-9160?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2018-9160, 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-2018-9160

Explore →

Is Your Infrastructure Affected by CVE-2018-9160?

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

Start Free Scan →Browse All CVEs