Skip to main content

Securly Chrome Extension CVE-2026-8879

| EUVDEUVD-2026-34165 HIGH
Inclusion of Functionality from Untrusted Control Sphere (CWE-829)
2026-06-03 certcc GHSA-jg8r-xqh5-556r
7.5
CVSS 3.1 · NVD
Share

Severity by source

NVD PRIMARY
7.5 HIGH
AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

Lifecycle Timeline

4
Analysis Generated
Jun 04, 2026 - 15:23 vuln.today
CVSS changed
Jun 04, 2026 - 15:22 NVD
7.5 (HIGH)
CVE Published
Jun 03, 2026 - 18:11 nvd
UNKNOWN (no severity yet)
CVE Published
Jun 03, 2026 - 18:11 nvd
HIGH 7.5

DescriptionCVE.org

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 NOT declared in manifest.json and bypasses Chrome Web Store static security review. It runs on all URLs and immediately hides all page content, creates a full-page overlay, pauses all videos, and only restores content when the service worker confirms the page passes filtering. If Securly's servers are unreachable, pages remain indefinitely hidden.

AnalysisAI

Denial of service in Securly Chrome Extension 3.0.7 allows remote attackers to render all web browsing unusable when the extension's filtering service is unreachable. The extension dynamically registers an undeclared content script (content13.min.js) at runtime via chrome.scripting.registerContentScripts(), hiding every page behind a full-page overlay until the service worker validates the page; if Securly's servers fail or are blocked, pages remain indefinitely blank. No public exploit identified at time of analysis, and EPSS rates exploitation probability at 0.02% (5th percentile).

Technical ContextAI

Securly is a school-oriented web filtering Chrome extension distributed via the Chrome Web Store. The flaw is rooted in CWE-829 (Inclusion of Functionality from Untrusted Control Sphere): rather than declaring its filtering content script in manifest.json - which would subject it to Google's static security review during Chrome Web Store submission - the extension uses chrome.scripting.registerContentScripts() at runtime to inject content13.min.js across all URLs (<all_urls>). The script hides DOM content, overlays the viewport, and pauses media, only releasing the page after the background service worker receives a positive filtering verdict from Securly's backend. This dynamic-injection design pattern circumvents the manifest review pipeline that browser vendors rely on to vet extension behavior.

RemediationAI

No vendor-released patch identified at time of analysis; neither the CERT/CC VU#595768 entry nor the NVD record cite a fixed version. Administrators deploying Securly in managed Chrome environments should monitor https://kb.cert.org/vuls/id/595768 for vendor response and, in the interim, consider compensating controls based on tolerance for the trade-offs: removing or disabling the extension via Google Workspace / Chrome Enterprise policy eliminates the DoS exposure but also removes the intended content filtering (likely unacceptable in K-12 deployments where Securly satisfies CIPA obligations); allowlisting and monitoring availability of Securly's filtering API endpoints (so outages are detected and triaged immediately) mitigates the operational impact without removing the extension; and preparing an emergency Chrome policy push that disables the extension fleet-wide gives operators a quick recovery path if Securly's backend suffers a prolonged outage. Reporting the manifest-bypass behavior to Google's Chrome Web Store team is also warranted since it represents a circumvention of static review.

More in Chrome

View all
CVE-2015-5122 CRITICAL POC
9.8 Jul 14

Use-after-free vulnerability in the DisplayObject class in the ActionScript 3 (AS3) implementation in Adobe Flash Player

CVE-2016-5198 HIGH POC
8.8 Jan 19

V8 in Google Chrome prior to 54.0.2840.90 for Linux, and 54.0.2840.85 for Android, and 54.0.2840.87 for Windows and Mac

CVE-2017-5070 HIGH POC
8.8 Oct 27

Type confusion in V8 in Google Chrome prior to 59.0.3071.86 for Linux, Windows, and Mac, and 59.0.3071.92 for Android, a

CVE-2016-1646 HIGH POC
8.8 Mar 29

The Array.prototype.concat implementation in builtins.cc in Google V8, as used in Google Chrome before 49.0.2623.108, do

CVE-2013-0758 CRITICAL POC
9.3 Jan 13

Mozilla Firefox before 18.0, Firefox ESR 10.x before 10.0.12 and 17.x before 17.0.2, Thunderbird before 17.0.2, Thunderb

CVE-2017-5030 HIGH POC
8.8 Apr 24

Incorrect handling of complex species in V8 in Google Chrome prior to 57.0.2987.98 for Linux, Windows, and Mac and 57.0.

CVE-2012-3993 CRITICAL POC
9.3 Oct 10

The Chrome Object Wrapper (COW) implementation in Mozilla Firefox before 16.0, Firefox ESR 10.x before 10.0.8, Thunderbi

CVE-2017-3823 HIGH POC
8.8 Feb 01

An issue was discovered in the Cisco WebEx Extension before 1.0.7 on Google Chrome, the ActiveTouch General Plugin Conta

CVE-2014-8636 HIGH POC
7.5 Jan 14

The XrayWrapper implementation in Mozilla Firefox before 35.0 and SeaMonkey before 2.32 does not properly interact with

CVE-2013-0757 CRITICAL POC
9.3 Jan 13

The Chrome Object Wrapper (COW) implementation in Mozilla Firefox before 18.0, Firefox ESR 17.x before 17.0.2, Thunderbi

CVE-2014-1510 CRITICAL POC
9.8 Mar 19

The Web IDL implementation in Mozilla Firefox before 28.0, Firefox ESR 24.x before 24.4, Thunderbird before 24.4, and Se

CVE-2015-5123 CRITICAL
9.8 Jul 14

Use-after-free vulnerability in the BitmapData class in the ActionScript 3 (AS3) implementation in Adobe Flash Player 13

Share

CVE-2026-8879 vulnerability details – vuln.today

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy