CVE-2026-8889
Modified Modified - Updated After Analysis
Deprecated SHA-1 Hashing in Securly Chrome Extension

Publication date: 2026-06-03

Last updated on: 2026-06-10

Assigner: CERT/CC

Description
Version 3.0.7 of the Securly Chrome Extension uses deprecated SHA-1 hashing for IWF CSAM URL matching (25,020 hashes) and CIPA blocklist matching (12,352 hashes).
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-06-03
Last Modified
2026-06-10
Generated
2026-06-24
AI Q&A
2026-06-03
EPSS Evaluated
2026-06-22
NVD
CVE-2026-8889
EUVD
EUVD-2026-34167
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
securly securly 3.0.7
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-407 An algorithm in a product has an inefficient worst-case computational complexity that may be detrimental to system performance and can be triggered by an attacker, typically using crafted manipulations that ensure that the worst case is being reached.
Attack-Flow Graph
AI Quick Actions
Instant insights powered by AI
Executive Summary

Version 3.0.7 of the Securly Chrome Extension uses deprecated SHA-1 hashing for matching URLs related to IWF CSAM (Child Sexual Abuse Material) and the CIPA blocklist.

Specifically, it uses SHA-1 hashes for 25,020 IWF CSAM URLs and 12,352 CIPA blocklist URLs, which is considered insecure because SHA-1 is a deprecated hashing algorithm vulnerable to collision attacks.

Impact Analysis

Using deprecated SHA-1 hashing can weaken the security of URL matching for harmful content filtering.

An attacker might exploit weaknesses in SHA-1 to bypass the filtering mechanisms, potentially allowing access to blocked or harmful URLs that should be restricted.

Chat Assistant
Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-8889. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70
EPSS Chart