PatchTheCVEsecurly vulnerabilities
Recent CVEs affecting securly products. 7 tracked.
securly has 7 tracked vulnerabilities, 0 critical. A fixed release or vendor patch exists for 0. Most recent: 2026-06-03. Highest priority: CVE-2026-8888 (score 41/100).
- CVE-2026-8888 HIGH 7.5 DOWNGRADE Version 3.0.7 of the Securly Chrome Extension downloads config.json over HTTP and compiles server-provided pat
- CVE-2026-8879 HIGH 7.5 DOWNGRADE Version 3.0.7 of the Securly Chrome Extension dynamically registers content13.min.js as a content script via c
- CVE-2026-8889 HIGH 7.5 DOWNGRADE Version 3.0.7 of the Securly Chrome Extension uses deprecated SHA-1 hashing for IWF CSAM URL matching (25,020
- CVE-2026-8876 HIGH 7.3 DOWNGRADE Version 3.0.7 of the Securly Chrome Extension contains hardcoded, plaintext AES passphrases in securly.min.js
- CVE-2026-8878 HIGH 7.5 DOWNGRADE Version 3.0.7 of the Securly Chrome Extension exposes multiple publicly accessible endpoints that allow unauth
- CVE-2026-8881 HIGH 7.5 DOWNGRADE Version 3.0.7 of the Securly Chrome Extension uses EVP_BytesToKey key derivation with MD5 and a single iterati
- CVE-2026-8874 HIGH 7.1 DOWNGRADE Version 3.0.7 of the Securly Chrome Extension downloads JSON files containing crisis alert keywords and filter
FAQ
How do I fix securly vulnerabilities?
Open the CVE for your version, check the affected range, then follow the listed action: upgrade to the fixed release, or downgrade or mitigate if no fix exists yet. Commands for each OS are shown on every CVE page.
Is securly being exploited right now?
None of the tracked securly CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which securly CVE should I patch first?
CVE-2026-8888 currently ranks highest (41/100): Version 3.0.7 of the Securly Chrome Extension downloads config.json over HTTP and compiles server-provided pat.