CVE-2026-8888

HIGHNVD 7.57.5
EchelonGraph scoreMEDIUM confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-06-03. NVD baseline CVSS 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 3 sources updated this week
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.5Exploit: None knownExposed: 0

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

Version 3.0.7 of the Securly Chrome Extension downloads config.json over HTTP and compiles server-provided patterns as JavaScript regular expressions via new RegExp() without complexity validation. An on-path attacker can inject specific patterns to cause catastrophic backtracking, resulting in denial of service on all browsing.

CVSS v3
7.5
EG Score
7.5(medium)
EG Risk
49(Track)
EG Risk 49/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
Severity75% × 45%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
36%
KEV
Not listed

Published

June 3, 2026

Last Modified

July 22, 2026

Advisory Details (1)

Auto-updated Jun 11, 2026
No patch confirmed yet. Sources: cert.
cert

VU#595768 - Securly Chrome Extension contains multiple weak encryption and access control vulnerabilities

https://kb.cert.org/vuls/id/595768

Vendor Advisories for CVE-2026-8888(1)

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

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 15× in last 7d / 93× 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 205 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-8888?
CVE-2026-8888 is a high vulnerability published on June 3, 2026. Version 3.0.7 of the Securly Chrome Extension downloads config.json over HTTP and compiles server-provided patterns as JavaScript regular expressions via new RegExp() without complexity validation. An on-path attacker can inject specific patterns to cause catastrophic backtracking, resulting in…
When was CVE-2026-8888 disclosed?
CVE-2026-8888 was first published in the National Vulnerability Database on June 3, 2026, with the most recent update on July 22, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-8888 actively exploited?
CVE-2026-8888 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 64.2% of all scored CVEs.
What is the CVSS score of CVE-2026-8888?
CVE-2026-8888 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-8888?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-8888, 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-2026-8888

Explore →

Is Your Infrastructure Affected by CVE-2026-8888?

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