# CVE-2026-33149: Tandoor Recipes Vulnerable to Host Header Injection

> Attackers can poison invite links via Host header injection, stealing tokens to take over accounts or access data.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 26 Mar 2026
- **Updated:** 30 Mar 2026
- **Also known as:** GHSA-x636-4jx6-xc4w

## What is CVE-2026-33149?

CVE-2026-33149 is a high-severity vulnerability in TandoorRecipes recipes, published on 26 Mar 2026. An attacker needs administrator access to exploit it, 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. Versions up to and including 2.5.3 set ALLOWED_HOSTS = '*' by default, which causes Django to accept any value in the HTTP Host header without validation. The application uses request.build_absolute_uri() to generate absolute URLs in multiple contexts, including invite link emails, API pagination, and OpenAPI schema generation. An attacker who can send requests to the application with a crafted Host header can manipulate all server-generated absolute URLs. The most critical impact is invite link poisoning: when an admin creates an invite and the application sends the invite email, the link points to the attacker's server instead of the real application. When the victim clicks the link, the invite token is sent to the attacker, who can then use it at the real application. As of time of publication, it is unknown if a patched version is available.

Weakness: CWE-644 (Improper Neutralization of HTTP Headers for Scripting Syntax)

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

It affects 1 product.


Products: Tandoor Recipes.

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

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

## Is CVE-2026-33149 being exploited?

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

Public exploit code:

- https://github.com/FilipeGaudard/CVE-2026-33149-PoC (github_poc): https://github.com/FilipeGaudard/CVE-2026-33149-PoC

## 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-33149 and fix it if it is affected.

What it is: CVE-2026-33149 is a high-severity vulnerability in TandoorRecipes recipes, published on 26 Mar 2026. An attacker needs administrator access to exploit it, 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-33149 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-33149/ (Markdown: https://insights.sbomify.com/CVE-2026-33149/index.md)
```

## Sources

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

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