Quick answers
- Is CVE-2026-109959 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-109959 being exploited in the wild.
- How severe is CVE-2026-109959?
- Medium severity, with a CVSS score of 4.3, published 13 October 2026.
- Which products and versions are affected?
- Espocrm 4.0.0 before 10.0.7.
- Is there a fix for CVE-2026-109959?
- 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-109959 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-109959?
- 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 vulnerability is an authorization bypass in the Note read endpoint (GET /Note/{id}) where the NoteAccessControl filter is not applied to audit data. Authenticated users with stream access to a parent record can request individual notes directly and recover the old and new values (data.attributes.was and became) of fields restricted by field-level security (FLS). The attack requires authentication and network access to the EspoCRM API, and only affects fields marked as audited.
Affected products
- EspoCRM EspoCRM 4.0.0 before 10.0.7
Timeline
- 2026-09-29: disclosed
- 2026-10-13: advisory