Skip to main content
VulnerabilityPublished

CVE-2026-8874: Securly Chrome Extension · Cleartext Transmission

Affects Securly Chrome ExtensionSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.1 High : upgrade to 3.0.7 soon.

Data as of 29 Oct 2026, 19:04 UTC

CVSS 3.1 base score
7.1High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 3% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 3.0.7
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 3 Jun 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

What to do

Upgrade Securly Chrome Extension to 3.0.7.

Affected software

ProductAffectedFixed in
SecurlySecurly Chrome ExtensionAffected
  • <3.0.7
Fixed in
  • 3.0.7

AI-suggested

If you cannot patch yet, users should be cautious about network environments where the extension is used, especially untrusted networks. Monitoring the vendor advisory at https://kb.cert.org/vuls/id/595768 is recommended for updates on remediation.

Description

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 the same extension correctly fetch IWF and CIPA data over HTTPS, demonstrating an inconsistent implementation of TLS.

References

Community reviews

Loading reviews…