# CVE-2026-35046: Tandoor has a Stored CSS Injection via <style> Tag in Recipe Instructions (API-Level)

> Authenticated users can inject CSS into recipes, enabling UI redressing and data exfiltration in clients rendering API output.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 6 Apr 2026
- **Updated:** 7 Apr 2026
- **Also known as:** GHSA-9hhh-g2fc-r8x2

## What is CVE-2026-35046?

CVE-2026-35046 is a medium-severity cross-site scripting vulnerability in TandoorRecipes recipes, published on 6 Apr 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

Tandoor Recipes is an application for managing recipes, planning meals, and building shopping lists. Prior to 2.6.4, Tandoor Recipes allows authenticated users to inject arbitrary <style> tags into recipe step instructions. The bleach.clean() sanitizer explicitly whitelists the <style> tag, causing the backend to persist and serve unsanitized CSS payloads via the API. Any client consuming instructions_markdown from the API and rendering it as HTML without additional sanitization will execute attacker-controlled CSS — enabling UI redressing, phishing overlays, visual defacement, and CSS-based data exfiltration. This vulnerability is fixed in 2.6.4.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

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

It affects 1 product.


Products: Tandoor Recipes.

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

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

## Is CVE-2026-35046 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-35046 exists.

## Other vulnerabilities in TandoorRecipes recipes

- [CVE-2025-23211](https://insights.sbomify.com/CVE-2025-23211/): Tandoor Recipes - SSTI - Remote Code Execution (critical 10.0)
- [CVE-2026-33152](https://insights.sbomify.com/CVE-2026-33152/): Tandoor Recipes Vulnerable to Unrestricted Brute-Force via BasicAuthentication (critical 9.1)
- [CVE-2025-23213](https://insights.sbomify.com/CVE-2025-23213/): Tandoor Recipes - Stored XSS through Unrestricted File Upload (high 8.7)
- [CVE-2026-35488](https://insights.sbomify.com/CVE-2026-35488/): Tandoor Recipes — CustomIsShared permits DELETE/PUT on RecipeBook by shared (read-only) users (high 8.1)
- [CVE-2026-35045](https://insights.sbomify.com/CVE-2026-35045/): Tandoor Recipes Affected by Private Recipe Exposure and Unauthorized Modification (high 8.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-35046 is a medium-severity cross-site scripting vulnerability in TandoorRecipes recipes, published on 6 Apr 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-35046 exists.

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

## Sources

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

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