Private recipe read/write via missing sub-resource authorization
Published Oct 16, 2026 · Updated Oct 16, 2026
Authorization bypass in Tandoor Recipes before 2.6.12 allows remote authenticated users to read and modify private recipes via the Step API. StepViewSet and IngredientViewSet accept Space membership through CustomIsUser instead of enforcing recipe ownership or sharing checks on supplied identifiers. Exploitation requires a normal user role, read/write API scope, and membership in the victim's Space; cross-Space access is outside the demonstrated impact.
Summary
What happened
Authorization bypass in Tandoor Recipes before 2.6.12 allows remote authenticated users to read and modify private recipes via the Step API. StepViewSet and IngredientViewSet accept Space membership through CustomIsUser instead of enforcing recipe ownership or sharing checks on supplied identifiers. Exploitation requires a normal user role, read/write API scope, and membership in the victim's Space; cross-Space access is outside the demonstrated impact.
The record
- CVE
- CVE-2026-61726
- Published
- Oct 16, 2026
- Updated
- Oct 16, 2026
- Vendor
- Tandoor Recipes
- Product
- Tandoor Recipes
- Classifications
- CWE-863, CWE-284, CWE-639, T1565.001
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 16, 2026CVE publishedPublication date reported by the CVE source.
- Oct 16, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 2.6.12
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
Public exploit references
- Private recipe Step API laboratory PoCproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started