# CVE-2026-8888: CVE-2026-8888

> An on-path attacker can cause browser denial of service by injecting malicious regex patterns into the Securly Chrome Extension's configuration.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Jun 2026
- **Updated:** 4 Jun 2026
- **Also known as:** GHSA-7w3m-2pw9-mg8x

## What is CVE-2026-8888?

CVE-2026-8888 is a high-severity denial of service vulnerability in Securly Chrome Extension, published on 3 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Version 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.

Weakness: CWE-917 (Improper Neutralization of Special Elements used in an Expression Language Statement), CWE-1333 (Inefficient Regular Expression Complexity)

## Which versions are affected by CVE-2026-8888?

It affects 1 product.


Products: Securly Securly.

## How do I fix CVE-2026-8888?

No fix has been published for CVE-2026-8888 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-8888 being exploited?

There is no known exploitation of CVE-2026-8888 in the wild and no public exploit code.

Public exploit code:

- https://github.com/George0Papasotiriou/CVE-2026-8888-Printer-Firmware-Unsigned-Update-via-HTTP (github_poc): https://github.com/George0Papasotiriou/CVE-2026-8888-Printer-Firmware-Unsigned-Update-via-HTTP

## Other vulnerabilities in Securly Chrome Extension

- [CVE-2026-8878](https://insights.sbomify.com/CVE-2026-8878/): CVE-2026-8878 (high 7.5)
- [CVE-2026-8879](https://insights.sbomify.com/CVE-2026-8879/): CVE-2026-8879 (high 7.5)
- [CVE-2026-8881](https://insights.sbomify.com/CVE-2026-8881/): CVE-2026-8881 (high 7.5)
- [CVE-2026-8889](https://insights.sbomify.com/CVE-2026-8889/): CVE-2026-8889 (high 7.5)
- [CVE-2026-8876](https://insights.sbomify.com/CVE-2026-8876/): CVE-2026-8876 (high 7.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-8888 and fix it if it is affected.

What it is: CVE-2026-8888 is a high-severity denial of service vulnerability in Securly Chrome Extension, published on 3 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-8888 in the wild and no public exploit code.

Affected product: Securly Chrome Extension. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-8888/ (Markdown: https://insights.sbomify.com/CVE-2026-8888/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-8888
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-8888
- OSV: https://osv.dev/vulnerability/CVE-2026-8888

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-8888/
Summaries are generated and may contain mistakes; the official description above is the record.