CVE-2026-8874

Filtering-rule manipulation via cleartext JSON downloads

Published Jun 3, 2026 · Updated Jun 3, 2026

Cleartext transmission in Securly Chrome Extension 3.0.7 allows man-in-the-middle attackers to alter filtering data over HTTP. The extension's Fetch API requests crisis-alert keyword and filtering-rule JSON from HTTP endpoints instead of applying TLS as it does for IWF and CIPA data. Exploitation requires an on-path position, enabling interception or modification of downloaded configuration and consequent exposure to blocked content or improper blocking.

CVSS severity7.1
High
EPSS probability0.14%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Cleartext transmission in Securly Chrome Extension 3.0.7 allows man-in-the-middle attackers to alter filtering data over HTTP. The extension's Fetch API requests crisis-alert keyword and filtering-rule JSON from HTTP endpoints instead of applying TLS as it does for IWF and CIPA data. Exploitation requires an on-path position, enabling interception or modification of downloaded configuration and consequent exposure to blocked content or improper blocking.

The record

CVE
CVE-2026-8874
Published
Jun 3, 2026
Updated
Jun 3, 2026
Vendor
Securly
Product
Securly Chrome Extension
Classifications
CWE-319, T1557
Attack vector
adjacent
Privileges
unauthenticated

Timeline

How it unfolded

  1. Jun 3, 2026CVE publishedPublication date reported by the CVE source.
  2. Jun 3, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=0 <3.0.7

What conditions does exploitation require?

Attack vectoradjacent
Required privilegesunauthenticated

What is affected?

Securly · Securly Chrome Extensionversion=0 <3.0.7

Published CVSS scores

7.1CISA-ADPCVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:N

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectoradjacent
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-319Cleartext Transmission of Sensitive Information
T1557Adversary-in-the-Middle

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo