CVE-2026-59963 json
Tandoor Recipes: Private recipe file and share-link authorization bypass in recipe utility API endpoints
published 4mo ago modified 23d ago also EUVD-2026-103142 , GHSA-cqj3-64qw-4w52
Unreviewed: the maintainers' own advisory
Published by the maintainers on their GitHub repository TandoorRecipes/recipes. GitHub has not reviewed it into the GitHub Advisory Database, so the affected packages and versions are the maintainers' word. Read the full advisory on GitHub.
- cvss
- 7.1
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 11%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- tandoor recipes 2.6.10
Is CVE-2026-59963 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 26d ago
Exploit prediction
0.21% chance of exploitation in the next 30 days, higher than 11% of all scored CVEs (FIRST EPSS, 2026-11-11).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.1 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N |
Affected products
- TandoorRecipes recipes
Classification
- Weakness
-
- CWE-639 Authorization Bypass Through User-Controlled Key
References
- github.com /TandoorRecipes/recipes/commit/82fd4e00f1387a1c466489989f2e94487149f7f4
- github.com /TandoorRecipes/recipes/commit/8b4a4c06902d024609d7376b6c45f5ea4f9bed07
-
github.com
/TandoorRecipes/recipes/security/advisories/GHSA-cqj3-64qw-4w52
advisory
- github.com /TandoorRecipes/recipes/releases/tag/2.6.10
Sources
- CVE List CVE-2026-59963
- NVD CVE-2026-59963
- Maintainer advisory GHSA-cqj3-64qw-4w52
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
The maintainers of TandoorRecipes/recipes published their own advisory on GitHub. Reviewed sources take precedence over it.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.