# CVE-2026-77460: EspoCRM: Mass email template renderer leaks restricted record fields

> Users with template edit access can leak restricted record fields in mass emails if per-user ACL application is disabled.

- **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:** 15 Oct 2026
- **Also known as:** GHSA-28w2-h88g-6vgv

## What is CVE-2026-77460?

CVE-2026-77460 is a medium-severity 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 10.0.3, a user with email-template edit access and mass-email sending access can reference restricted record fields in a template because the renderer stops filtering those fields when per-user ACL application is disabled. The same behavior affects group email auto-replies when a regular user can edit the selected template, even though an administrator controls the group email. Rendered messages can disclose restricted user fields. This issue is fixed in version 10.0.3.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

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


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

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

## Is CVE-2026-77460 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-77460 is a medium-severity 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-77460 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-77460/ (Markdown: https://insights.sbomify.com/CVE-2026-77460/index.md)
```

## Sources

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

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