# CVE-2026-75505: EspoCRM: Access control bypass in Mass Update letting regular user with Mass Update permission read any attachment

> Authenticated users with mass-update permissions can read arbitrary attachments by bypassing access controls, exposing sensitive file contents.

- **Severity:** Medium 6.0 (`CVSS:4.0/AV:N/AC:H/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA: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-24pg-2q7q-m5p6

## What is CVE-2026-75505?

CVE-2026-75505 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 10.0.2, an authenticated user with mass-update permission can supply a known attachment identifier to the mass-update functionality. The mass-update processor duplicates the attachment without checking whether the caller can read it, bypassing record-level and field-level restrictions and exposing the file contents through the copied attachment. Obtaining a valid attachment identifier may be difficult. This issue is fixed in version 10.0.2.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-75505 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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