CVE-2026-8889

CVE-2026-8889

Published Jun 3, 2026 CVSS 3.1 · 7.5 High EPSS < 1% KEV · Not listed
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).

Analysis

AI-generated

Technical impact

Version 3.0.7 of the Securly Chrome Extension relies on SHA-1 hashing to match IWF CSAM URLs and CIPA blocklist entries. This weakness corresponds to CWE‑407, Weak Hash Function. SHA-1 is considered weak because collisions can be produced in reasonable time, which could allow an attacker to craft a hash that mimics a disallowed or blocked URL. The result would be the extension treating inappropriate content as allowed or wrongly blocking legitimate content, undermining its purpose of protecting children and other users. Based on the description, it is inferred that an attacker could potentially generate a collision that would bypass the extension’s filtering logic.

Affected Systems

The Securly Chrome Extension, version 3.0.7, is affected. No other versions or related products were mentioned in the advisory.

Risk and Exploitability

The CVSS score is 7.5 and the EPSS score is < 1%, indicating that no publicly documented exploitation has yet been reported. The likely attack requires an attacker to produce a SHA-1 collision, a computationally intensive task that may not be practical in the short term. Nonetheless, the use of a broken hash algorithm compromises policy enforcement, and the absence of a KEV listing does not negate the potential impact.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade the Securly Chrome Extension to a version that replaces SHA‑1 with a modern hash algorithm such as SHA‑256.
  • If no updated version is available, uninstall or disable the extension to prevent the possibility of content filtering bypass.
  • Replace the SHA‑1 implementation in the extension’s hash verification logic with a secure hash algorithm, if custom development is possible.
  • Monitor Securly’s security advisories and support channels for new releases that address the hashing issue.
  • Consider deploying an alternative content‑filtering solution that employs secure cryptographic primitives.

Generated by OpenCVE AI on June 6, 2026 at 00:50 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
References
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
Weaknesses CWE-327
Type Values Removed Values Added
First Time appeared Securly securly
Weaknesses CWE-407
CPEs cpe:2.3:a:securly:securly:3.0.7:*:*:*:*:chrome:*:*
Vendors & Products Securly securly
Metrics cvssV3_1

{'score': 7.5, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N'}

Type Values Removed Values Added
First Time appeared Securly
Securly securly Chrome Extension
Vendors & Products Securly
Securly securly Chrome Extension
Type Values Removed Values Added
Weaknesses CWE-327
Type Values Removed Values Added
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).
Title CVE-2026-8889
References
Weaknesses
  • CWE-407

    Inefficient Algorithmic Complexity

Sources

Status
PUBLISHED
Assigner
certcc
Published
Updated
Jun 10, 2026, 7:00 PM
Reserved
May 18, 2026, 8:43 PM
Status
Modified
Published
Jun 3, 2026, 7:16 PM
Modified
Jul 22, 2026, 8:10 PM