Quick answers
- Is CVE-2026-118686 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-118686 being exploited in the wild.
- How severe is CVE-2026-118686?
- High severity, with a CVSS score of 7.5, published 28 October 2026.
- Which products and versions are affected?
- Espocrm 9.3.10 and below; 10.0.7 and below.
- Is there a fix for CVE-2026-118686?
- Yes: fixed in EspoCRM 9.3.11, 10.0.8. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-118686 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-118686?
- Check whether you run Espocrm at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: EspoCRM 9.3.11, 10.0.8
Technical details
The password-redaction regular expression applied during API error handling in EspoCRM exhibits ReDoS (Regular Expression Denial of Service) behavior when processing long request bodies, consuming excessive CPU cycles. An unauthenticated network attacker can send concurrent large API requests to exhaust available server workers. The vulnerability affects EspoCRM versions 9.3.10 and below, and 10.0.7 and below, with patches available in 9.3.11 and 10.0.8 respectively.
Affected products
- EspoCRM EspoCRM 9.3.10 and below; 10.0.7 and below
Timeline
- 2026-10-28: disclosed
- 2026-10-13: advisory: GitHub Security Advisory GHSA-6pjq-v35w-jmjh published