The number and severity of CVEs published that impact products developed by Securly over time
Signals from CVEs in this vendor scope (7 CVEs).
7 CVEs · Highest risk first
| CVE | Published | CVSS | Risk | KEV | Exploit |
|---|---|---|---|---|---|
CVE-2026-8888HIGH 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 compl | Jun 3, 2026 | 7.5 | 32 | NO | NO |
CVE-2026-8889HIGH 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). | Jun 3, 2026 | 7.5 | 32 | NO | NO |
CVE-2026-8881HIGH Version 3.0.7 of the Securly Chrome Extension uses EVP_BytesToKey key derivation with MD5 and a single iteration for AES encryption. MD5 has been broken since 2004 and a single ite | Jun 3, 2026 | 7.5 | 32 | NO | NO |
CVE-2026-8876HIGH Version 3.0.7 of the Securly Chrome Extension contains hardcoded, plaintext AES passphrases in securly.min.js. These keys decrypt crisis alert keyword data and intervention site da | Jun 3, 2026 | 7.3 | 32 | NO | NO |
CVE-2026-8879HIGH Version 3.0.7 of the Securly Chrome Extension dynamically registers content13.min.js as a content script via chrome.scripting.registerContentScripts() at runtime. This script is NO | Jun 3, 2026 | 7.5 | 31 | NO | NO |
CVE-2026-8878HIGH Version 3.0.7 of the Securly Chrome Extension exposes multiple publicly accessible endpoints that allow unauthenticated access to sensitive data. The exposed information consists o | Jun 3, 2026 | 7.5 | 31 | NO | NO |
CVE-2026-8874HIGH Version 3.0.7 of the Securly Chrome Extension downloads JSON files containing crisis alert keywords and filtering rules over unencrypted HTTP via the Fetch API. Other endpoints in | Jun 3, 2026 | 7.1 | 30 | NO | NO |
Signals from CVEs in this vendor scope (7 CVEs).
An overview of all social media posts that mention a CVE ID that affects a product developed by Securly.
Media articles that mention a CVE ID that affects a product developed by Securly — matched by CVE ID, not by vendor name.