Quick answers
- Is CVE-2026-46694 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-46694 being exploited in the wild.
- How severe is CVE-2026-46694?
- Medium severity, with a CVSS score of 6.5, published 15 October 2026.
- Which products and versions are affected?
- Espocrm prior to 9.3.7.
- Is there a fix for CVE-2026-46694?
- Yes: fixed in 9.3.7. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-46694 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-46694?
- 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: 9.3.7
Technical details
The vulnerability exists in the portal Note API access control logic: while stream list responses properly filter out notes with isInternal set to true, the direct single-note fetch endpoint (checkEntityRead) does not enforce the same restriction. An authenticated portal user can bypass the access check by making a direct API request if they know the note identifier, allowing them to read notes intended only for internal agents. The fix adds an explicit isInternal() check in the AclPortal\Note\AccessChecker to deny access to internal notes at read time.
Affected products
- EspoCRM EspoCRM prior to 9.3.7
Timeline
- 2026-10-15: disclosed
- 2026-05-18: patched