# CVE-2026-112342: Tandoor Recipes < 2.7.0 Cross-Space Permission Cache Poisoning


- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 23 Oct 2026
- **Updated:** 27 Oct 2026
- **Also known as:** GHSA-69q3-5q6x-7hmx

## What is CVE-2026-112342?

CVE-2026-112342 is a high-severity vulnerability in Tandoor Recipes, published on 23 Oct 2026. 

### Official description

Tandoor Recipes before 2.7.0 contains an improper cache-key design in cookbook/helper/permission_helper.py that allows authenticated users to retain stale group-based permissions across different spaces by exploiting a cache key keyed only on user id while omitting the active space, with the cached entry's TTL refreshed on every request. Attackers can create their own space to obtain an admin group designation, then switch their active space to a victim space where they hold lesser privileges, causing the stale cached admin decision to authorize elevated access and bypass group revocations or demotions across multiple permission classes and views.

Weakness: CWE-863 (Incorrect Authorization)

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


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

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

## Is CVE-2026-112342 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-112342 is a high-severity vulnerability in Tandoor Recipes, published on 23 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-112342 in the wild and no public exploit code.

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

## Sources

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

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