CVE-2018-19131

MEDIUMNVD 6.16.1—
EchelonGraph scoreMEDIUM confidence

Score 6.1 from GitHub Security Advisory published 2022-05-14. NVD baseline CVSS 6.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Elevated
6.1EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 3.3%CVSS: 6.1Exploit: Elevated riskExposed services: Not assessed

A fix is available — apply it.

Squid before 4.4 has XSS via a crafted X.509 certificate during HTTP(S) error page generation for certificate errors.

CVSS v3
6.1
EG Score
6.1MEDIUMmedium confidence
EG Risk
48
EG Risk 48/100CISA SSVC

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
Severity61% × 45%
Exploitation40% × 40%
Automatability30% × 15%
CISA SSVC: Track at low or medium mission impact; Track* or Attend at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
3.3%
EPSS %ILE
88th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track* or Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (EG-KEV: elevated) · Automatable unknown (not published for this CVE) · Technical impact partial (CVSS below 9.0). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

November 9, 2018

Last Modified

November 21, 2024

References (6)

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
squid—
  • every version up to 4.4-1: fixed in 4.4-1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
squid—
  • every version up to 4.4-1: fixed in 4.4-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
squid—
  • every version up to 4.4-1: fixed in 4.4-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
squid—
  • every version up to 4.4-1: fixed in 4.4-1
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 5× in last 7d / 21× 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 160 total refreshes for this CVE.

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

Publicly available exploits

(1 reference)

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

  • GitHub PoCJonathanWilbur/CVE-2018-19131
    First seen Nov 13, 2018

    Proof-of-Concept exploit of CVE-2018-19131: Squid Proxy XSS via X.509 Certificate

    Open source ↗

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2018-19131?
CVE-2018-19131 is a medium vulnerability published on November 9, 2018. Squid before 4.4 has XSS via a crafted X.509 certificate during HTTP(S) error page generation for certificate errors.
When was CVE-2018-19131 disclosed?
CVE-2018-19131 was first published on November 9, 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-19131 actively exploited?
CVE-2018-19131 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 3.3% probability of exploitation in the next 30 days (88th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2018-19131?
CVE-2018-19131 has a CVSS v3 base score of 6.1 (NVD).
How do I remediate CVE-2018-19131?
A fix for CVE-2018-19131 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2018-19131

Explore →

Is Your Infrastructure Affected by CVE-2018-19131?

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

Book a Demo →Browse All CVEs