CVE-2026-8888
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedVersion 3.0.7 of the Securly Chrome Extension downloads config.json over HTTP and compiles server-provided patterns as JavaScript regular expressions via new RegExp() without complexity validation. An on-path attacker can inject specific patterns to cause catastrophic backtracking, resulting in denial of service on all browsing.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe Securly Chrome Extension v3.0.7 fetches its configuration file over unencrypted HTTP, allowing an on-path attacker to inject malicious content. The extension then compiles server-provided patterns directly as JavaScript regular expressions using new RegExp() without any complexity or backtracking validation, enabling attackers to inject crafted regex patterns that cause catastrophic backtracking and crash the browser tab.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 3.0.7CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify Securly Chrome Extension versionOpen Chrome, navigate to chrome://extensions, enable Developer Mode in the top right, locate the Securly extension in the list, and read the version number displayed under the extension nameAffected if The installed version is exactly 3.0.7
-
Inspect network traffic for config downloadOpen Chrome DevTools (F12), go to the Network tab, reload the browser or trigger the extension, filter for 'config.json' requests, and examine the protocol column to see if the request uses HTTP or HTTPSAffected if The extension makes a request to config.json using the HTTP protocol (http://) instead of HTTPS (https://)
-
Examine extension source code for regex compilationIn chrome://extensions, find the Securly extension, click 'Details', then click 'View in Chrome Web Store' or use 'Pack extension' to extract the CRX file, then inspect background.js or similar scripts for usage of new RegExp() with server-supplied data without complexity validationAffected if The extension code contains new RegExp() calls that accept remote configuration data without validating regex complexity or backtracking limits
You are affected if you have Securly Chrome Extension version 3.0.7 installed AND the extension downloads its configuration over unencrypted HTTP AND the extension compiles remote patterns as regex without validation.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataEnforce HTTPS for all configuration downloads to prevent injection, and implement regex complexity validation (e.g., length limits, analysis of nested quantifiers) before compiling patterns with new RegExp(), or use a safe regex execution sandbox with timeouts.
- Consultation4.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-8888 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-8888 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data