# CVE-2026-35045: Tandoor Recipes Affected by Private Recipe Exposure and Unauthorized Modification

> Authenticated users can modify or expose private recipes in Tandoor Recipes due to missing authorization checks on the batch update endpoint.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/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:** 6 Apr 2026
- **Updated:** 7 Apr 2026
- **Also known as:** GHSA-v8x3-w674-55p5

## What is CVE-2026-35045?

CVE-2026-35045 is a high-severity missing authorization vulnerability in TandoorRecipes recipes, published on 6 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Tandoor Recipes is an application for managing recipes, planning meals, and building shopping lists. Prior to 2.6.4, the PUT /api/recipe/batch_update/ endpoint in Tandoor Recipes allows any authenticated user within a Space to modify any recipe in that Space, including recipes marked as private by other users. This bypasses all object-level authorization checks enforced on standard single-recipe endpoints (PUT /api/recipe/{id}/), enabling forced exposure of private recipes, unauthorized self-grant of access via the shared list, and metadata tampering. This vulnerability is fixed in 2.6.4.

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

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

It affects 1 product.


Products: Tandoor Recipes.

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

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

## Is CVE-2026-35045 being exploited?

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

Public exploit code:

- https://github.com/FilipeGaudard/CVE-2026-35045-PoC (github_poc): https://github.com/FilipeGaudard/CVE-2026-35045-PoC

## Other vulnerabilities in TandoorRecipes recipes

- [CVE-2025-23211](https://insights.sbomify.com/CVE-2025-23211/): Tandoor Recipes - SSTI - Remote Code Execution (critical 10.0)
- [CVE-2026-33152](https://insights.sbomify.com/CVE-2026-33152/): Tandoor Recipes Vulnerable to Unrestricted Brute-Force via BasicAuthentication (critical 9.1)
- [CVE-2025-23213](https://insights.sbomify.com/CVE-2025-23213/): Tandoor Recipes - Stored XSS through Unrestricted File Upload (high 8.7)
- [CVE-2026-35488](https://insights.sbomify.com/CVE-2026-35488/): Tandoor Recipes — CustomIsShared permits DELETE/PUT on RecipeBook by shared (read-only) users (high 8.1)
- [CVE-2026-33149](https://insights.sbomify.com/CVE-2026-33149/): Tandoor Recipes Vulnerable to Host Header Injection (high 8.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-35045 is a high-severity missing authorization vulnerability in TandoorRecipes recipes, published on 6 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-35045 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-35045/ (Markdown: https://insights.sbomify.com/CVE-2026-35045/index.md)
```

## Sources

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

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