Raw vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:NSummary
CVE-2026-35045 is a high-severity Authorization Bypass Through User-Controlled Key (CWE-639) vulnerability in Tandoor Recipes. Its CVSS base score is 8.1 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 19th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
The strongest mitigations our analysis identified map to AC-24 (Access Control Decisions) and AC-3 (Access Enforcement) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2026-35045 is an authorization bypass vulnerability in Tandoor Recipes, a self-hosted web application for managing recipes, planning meals, and building shopping lists. In versions prior to 2.6.4, the PUT /api/recipe/batch_update/ endpoint fails to enforce proper object-level access controls, allowing any authenticated user within a shared Space to modify recipes owned by other users, including those explicitly marked as private. This circumvents the authorization checks present in standard single-recipe endpoints like PUT /api/recipe/{id}/, and is classified under CWE-639 (Authorization Bypass Through User-Controlled Key). The vulnerability carries a CVSS v3.1 base score of 8.1 (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N), reflecting high confidentiality and integrity impacts.
An attacker requires only low-privilege authentication as a user within the target Space to exploit this issue remotely over the network with no user interaction. Successful exploitation enables reading and modifying private recipes, injecting or altering content to force exposure, self-granting access through manipulation of shared lists, and tampering with recipe metadata. These actions could lead to unauthorized data disclosure, recipe corruption, or privilege escalation within the Space, potentially compromising the confidentiality and integrity of user-managed content across the application.
The vulnerability is addressed in Tandoor Recipes version 2.6.4, as detailed in the project's release notes and security advisory. Security practitioners should upgrade to 2.6.4 or later, review access controls in multi-user Spaces, and audit batch update endpoints for similar bypasses in custom deployments. Relevant resources include the GitHub release at https://github.com/TandoorRecipes/recipes/releases/tag/2.6.4 and the advisory at https://github.com/TandoorRecipes/recipes/security/advisories/GHSA-v8x3-w674-55p5.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-19388
Vulnerability Data
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…
more
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.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
Enforcing approved authorizations on every access request structurally stops a user-controlled key from reaching another user's data.
Requiring explicit access-control decisions on each request blocks unauthorized key-driven access.
Least-privilege restrictions limit the scope of data reachable even if a key check is bypassed.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Enforcing authorization policy and least privilege directly blocks user-controlled key tampering that bypasses access checks.
Logical access controls prevent unauthorized data access that results from missing authorization checks on object references.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing can detect missing authorization checks but does not prevent the weakness in production.
Information access restriction explicitly enforces that users may only retrieve data they are authorized to see, directly addressing user-controlled key bypass.
Access control policy directly requires enforcement of authorization rules that prevent unauthorized access via manipulated keys.
Managing access rights includes ensuring users can only access their own records and not bypass authorization by altering identifiers.
Privileged access rights control restricts what data each user may access, mitigating direct object reference attacks.
Secure development lifecycle includes authorization design but does not itself implement runtime access checks.