# CVE-2026-59963: Tandoor Recipes: Private recipe file and share-link authorization bypass in recipe utility API endpoints

> Authenticated users can access private recipe files and create public share links without proper authorization checks, exposing sensitive data.

- **Severity:** High 7.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/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:** 16 Oct 2026
- **Updated:** 16 Oct 2026
- **Also known as:** GHSA-cqj3-64qw-4w52

## What is CVE-2026-59963?

CVE-2026-59963 is a high-severity missing authorization vulnerability in TandoorRecipes recipes, published on 16 Oct 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.10, recipe utility endpoints retrieve same-Space Recipe objects without invoking the private-recipe owner or sharing permission when an authenticated member of a shared Space supplies another member's private recipe identifier to AI import, file, external-link, or share-link endpoints. Request processing uses api/ai-import/, api/get_recipe_file/, api/get_external_file_link/, api/share-link/, CustomRecipePermission. The attack works because the endpoints read private recipe files, send file bytes to the configured AI provider, or create and disclose external links without object-level authorization, and api/share-link/ can create a public link when Space sharing is enabled. This can expose private recipe files and sensitive uploaded content to another same-Space user and to configured external services. This issue is fixed in version 2.6.10.

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

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


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

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

## Is CVE-2026-59963 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-59963 is a high-severity missing authorization vulnerability in TandoorRecipes recipes, published on 16 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-59963 in the wild and no public exploit code.

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

## Sources

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

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