# CVE-2026-115810: Tandoor Recipes before 2.7.0 SSRF via Pestle Importer Image URL


- **Severity:** Medium 6.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:N/SC:H/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 23 Oct 2026
- **Updated:** 29 Oct 2026
- **Also known as:** GHSA-2rvv-3hmc-xc55, GHSA-xq7g-9q95-vjc6

## What is CVE-2026-115810?

CVE-2026-115810 is a medium-severity vulnerability in TandoorRecipes recipes, published on 23 Oct 2026. 

### Official description

Tandoor Recipes before 2.7.0 contains a server-side request forgery vulnerability in the Pestle importer that allows authenticated low-privileged users to force the server to issue GET requests to arbitrary internal or external hosts by crafting a malicious image URL in a Pestle JSON import file. Attackers can exploit the raw requests.get call in cookbook/integration/pestle.py, which bypasses the application's centralized requests-hardened SSRF filter, to reach internal-only endpoints, perform port/service discovery, and exfiltrate internal responses via the stored recipe image.

Weakness: CWE-918 (Server-Side Request Forgery)

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


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

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

## Is CVE-2026-115810 being exploited?

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

## Fix prompt for AI coding agents

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

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

Affected product: TandoorRecipes recipes. 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-115810/ (Markdown: https://insights.sbomify.com/CVE-2026-115810/index.md)
```

## Sources

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

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