# CVE-2026-113643: EspoCRM PDF Rendering Pipeline ImageSourceProvider.php get authorization


- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:X`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 20 Oct 2026
- **Updated:** 20 Oct 2026
- **Also known as:** GHSA-w8vm-3g62-56g7

## What is CVE-2026-113643?

CVE-2026-113643 is a medium-severity vulnerability in EspoCRM, published on 20 Oct 2026. 

### Official description

A vulnerability was found in EspoCRM up to 9.3.10/10.0.10. This affects the function ImageSourceProvider::get of the file application/Espo/Tools/Pdf/Dompdf/ImageSourceProvider.php of the component PDF Rendering Pipeline. Performing a manipulation of the argument ID results in authorization bypass. The attack may be initiated remotely. The patch is named 91a9edbcedb9c7aa8e3d3ac81d8a7acccb99bca2. It is suggested to install a patch to address this issue.

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

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


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

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

## Is CVE-2026-113643 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-113643 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-113643 is a medium-severity vulnerability in EspoCRM, published on 20 Oct 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-113643 exists.

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

## Sources

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

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