VYPR
Unrated severityNVD Advisory· Published Jun 3, 2026

CVE-2026-8879

CVE-2026-8879

Description

Securly Chrome Extension 3.0.7 bypasses security reviews by dynamically registering unlisted content scripts, leading to page content hiding and potential DoS.

AI Insight

LLM-synthesized narrative grounded in this CVE's description and references.

Securly Chrome Extension 3.0.7 bypasses security reviews by dynamically registering unlisted content scripts, leading to page content hiding and potential DoS.

Vulnerability

Version 3.0.7 of the Securly Chrome Extension dynamically registers content13.min.js as a content script using chrome.scripting.registerContentScripts() at runtime. This script is not declared in manifest.json, allowing it to bypass Chrome Web Store static security reviews. It is designed to run on all URLs [1].

Exploitation

An attacker with the ability to make Securly's servers unreachable could exploit this vulnerability. When the extension cannot confirm the page passes filtering with its service worker, the page content remains hidden indefinitely, effectively causing a denial of service [1].

Impact

Successful exploitation can lead to a denial of service (DoS) by indefinitely hiding all page content for users of the Securly Chrome Extension. This impacts the usability of web pages for students in managed environments [1].

Mitigation

No specific patch version or release date is mentioned in the available references. Users are advised to monitor Securly for updates. As of the publication of this advisory, there are no known workarounds or indicators of compromise. The extension is widely used in K-12 school-managed Chromebooks [1].

AI Insight generated on Jun 3, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.

Affected products

1

Patches

0

No patches discovered yet.

Vulnerability mechanics

No source-code context for this CVE — mechanics is only generated when we can read the actual fix diff. Without that, the four sections (root cause, attack vector, affected code, fix) would be speculation rather than analysis.

References

1

News mentions

0

No linked articles in our index yet.