# CVE-2026-46694: EspoCRM: Portal User ACL Bypass Exposes Internal Stream Notes

> Portal users can bypass access controls to read internal agent notes via the API, exposing sensitive internal data.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Oct 2026
- **Updated:** 16 Oct 2026
- **Also known as:** GHSA-cg9f-34hj-p238

## What is CVE-2026-46694?

CVE-2026-46694 is a medium-severity missing authorization vulnerability in espocrm, published on 15 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

EspoCRM is an open source customer relationship management application. Prior to 9.3.7, a portal user with stream access to a parent record can directly fetch a Note through the portal Note API and read an internal stream note when the note identifier is known. Stream list responses correctly hide notes whose isInternal field is true, but the direct single-Note access check does not enforce that restriction, exposing internal agent content. This issue is fixed in version 9.3.7.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-46694 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-46694 is a medium-severity missing authorization vulnerability in espocrm, published on 15 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-46694 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-46694/ (Markdown: https://insights.sbomify.com/CVE-2026-46694/index.md)
```

## Sources

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

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