Quick answers
- Is CVE-2026-109958 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-109958 being exploited in the wild.
- How severe is CVE-2026-109958?
- Medium severity, with a CVSS score of 4.3, published 13 October 2026.
- Which products and versions are affected?
- Espocrm 4.0.0 through 10.0.6.
- Is there a fix for CVE-2026-109958?
- Yes: fixed in 10.0.7. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-109958 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-109958?
- 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: 10.0.7
Technical details
The address-book search API endpoint fails to enforce field-level access control (ACL) checks on the emailAddress field, allowing authenticated users to retrieve email addresses even when their role restricts access to that field. The vulnerability requires the attacker to already have access to records and network access to the API. This is an authorization bypass affecting confidentiality only, with a fix available in version 10.0.7.
Affected products
- EspoCRM EspoCRM 4.0.0 through 10.0.6
Timeline
- 2026-09-29: disclosed: GitHub Security Advisory GHSA-2cr7-9g4f-8723 published
- 2026-10-13: advisory: NVD CVE-2026-109958 published