Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:LSummary
CVE-2026-35489 is a high-severity Authorization Bypass Through User-Controlled Key (CWE-639) vulnerability in Tandoor Recipes. Its CVSS base score is 7.3 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked at the 13th 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-35489 affects Tandoor Recipes, a self-hosted web application for managing recipes, planning meals, and building shopping lists, in versions prior to 2.6.4. The vulnerability resides in the POST /api/food/{id}/shopping/ endpoint, which directly reads the amount and unit fields from request.data without validation before passing them to ShoppingListEntry.objects.create(). This leads to two issues: supplying invalid (non-numeric) amount values triggers an unhandled exception resulting in an HTTP 500 error, and providing a unit ID from a different Space enables cross-space association of foreign-key references, leaking data across tenant boundaries. Unlike other endpoints that use the ShoppingListEntrySerializer for validation and sanitization, this endpoint lacks such protections. The issue carries a CVSS v3.1 base score of 7.3 (AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L) and is associated with CWE-639 (Authorization Bypass Through User-Controlled Key) and CWE-1284 (Improper Validation of Specified Quantity in Input).
The vulnerability is exploitable remotely over the network by unauthenticated attackers with no privileges required and low complexity. An attacker can send a crafted POST request to the vulnerable endpoint: non-numeric strings in the amount field cause a server-side crash and HTTP 500 response, enabling denial-of-service; a unit ID belonging to another tenant's Space allows improper association, potentially leaking sensitive foreign-key references and enabling cross-tenant data inference or manipulation.
The vulnerability is addressed in Tandoor Recipes version 2.6.4, as detailed in the project's release notes and GitHub security advisory GHSA-8w8h-3pv2-3554. Security practitioners should upgrade to 2.6.4 or later to apply the fix, which presumably adds proper validation via the ShoppingListEntrySerializer or equivalent sanitization to the affected endpoint.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-19674
Vulnerability Data
Tandoor Recipes is an application for managing recipes, planning meals, and building shopping lists. Prior to 2.6.4, the POST /api/food/{id}/shopping/ endpoint reads amount and unit directly from request.data and passes them without validation to ShoppingListEntry.objects.create(). Invalid amount values (non-numeric strings)…
more
cause an unhandled exception and HTTP 500. A unit ID from a different Space can be associated cross-space, leaking foreign-key references across tenant boundaries. All other endpoints creating ShoppingListEntry use ShoppingListEntrySerializer, which validates and sanitizes these fields. 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
Control response
—
—
—
V6.7.2V1.4.2V2.1.1V2.2.1
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.
SI-10 requires validity checks on information inputs, directly stopping acceptance of malformed quantities before they can be used.
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.
Secure SDLC practices directly require proper quantity/length validation in input handling.
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.