# CVE-2026-118686: EspoCRM before 9.3.11 and 10.0.8 Unauthenticated Denial of Service via Password-Redaction Regex


- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 28 Oct 2026
- **Updated:** 28 Oct 2026
- **Also known as:** GHSA-6pjq-v35w-jmjh, GHSA-jv3j-8935-75r6

## What is CVE-2026-118686?

CVE-2026-118686 is a high-severity vulnerability in espocrm, published on 28 Oct 2026. 

### Official description

EspoCRM before 9.3.11 and 10.x before 10.0.8 contains a denial of service vulnerability in which the password-redaction regular expression applied during API error handling consumes excessive CPU on long request bodies. Unauthenticated remote attackers can concurrently send a small number of large API requests to exhaust server workers, making EspoCRM slow or unavailable to legitimate users.

Weakness: CWE-1333 (Inefficient Regular Expression Complexity)

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


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

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

## Is CVE-2026-118686 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-118686 is a high-severity vulnerability in espocrm, published on 28 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-118686 in the wild and no public exploit code.

Affected product: espocrm. 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-118686/ (Markdown: https://insights.sbomify.com/CVE-2026-118686/index.md)
```

## Sources

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

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