Securly Chrome Extension: Cleartext Transmission of Sensitive Information
CVE-2026-8874 is a high-severity cleartext transmission of sensitive information vulnerability in Securly Chrome Extension from Securly, with a CVSS 3.1 base score of 7.1 out of 10. It can be exploited from the same local network by an unauthenticated attacker, without any action from a user. The record lists version 3.0.7 as the first without the flaw, so updating Securly Chrome Extension to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.14% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update Securly Chrome Extension to 3.0.7 or a later version.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Securly | Securly Chrome Extension | before 3.0.7 | 3.0.7 |
| Securly | Securly | 3.0.7 | Not stated |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- AdjacentThe attacker must be on the same local network segment.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- LowSome restricted data can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- NoneAvailability is not affected.
Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:N. Scored by CISA (ADP).
Official 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.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Cleartext Transmission of Sensitive Information
The product transmits sensitive or security-critical data in cleartext in a communication channel that can be sniffed by unauthorized actors.
How developers prevent this class of flaw
- Before transmitting, encrypt the data using reliable, confidentiality-protecting cryptographic protocols.
- When using web applications with SSL, use SSL for the entire session from login to logout, not just for the initial login page.
- When designing hardware platforms, ensure that approved encryption algorithms (such as those recommended by NIST) protect paths from security critical data to trusted user applications.
More Cleartext Transmission of Sensitive Information vulnerabilities (CWE-319)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: partial).
- Record last changed materially (score, affected products, status or references).
References
Third-party and government advisories
- kb.cert.org/vuls/id/595768Third Party Advisory
Other vulnerabilities in Securly Chrome Extension
- 7.5 High severity
- 7.5 High severity
- 7.5 High severity
- 7.5 High severity
- 7.3 High severity
Recent Cleartext Transmission of Sensitive Information vulnerabilities
- 7.5 High severity
- 9.8 Critical severity
- 7.5 High severity
- 7.5 High severity
- 9.1 Critical severity
- 8.8 High severity
Spotted an error? Tell us.