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

High 8.1 Published 6 Apr 2026 Updated 7 Apr 2026

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

Exploited in the wild: Not known
Login needed: Any signed-in user
Attackable: Over the internet
Victim action needed: Not needed
Fix: None listed

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

Which versions are affected by CVE-2026-35045?

It affects 1 product.

Products include 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.

Upgrade, and check permissions on every request on the server, not only in the interface. More about Missing authorization.

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: 1 proofs of concept on GitHub.

Sources

Also known as GHSA-v8x3-w674-55p5.