# CVE-2026-25964: Tandoor Recipes Affected by Authenticated Local File Disclosure (LFD) via Recipe Import leads to Arbitrary File Read

> Authenticated users can read arbitrary server files via path traversal in recipe import, exposing sensitive system and configuration data.

- **Severity:** Medium 4.9 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Feb 2026
- **Updated:** 13 Feb 2026
- **Also known as:** GHSA-6485-jr28-52xx

## What is CVE-2026-25964?

CVE-2026-25964 is a medium-severity path traversal vulnerability in TandoorRecipes recipes, published on 13 Feb 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Tandoor Recipes is an application for managing recipes, planning meals, and building shopping lists. Prior to 2.5.1, a Path Traversal vulnerability in the RecipeImport workflow of Tandoor Recipes allows authenticated users with import permissions to read arbitrary files on the server. This vulnerability stems from a lack of input validation in the file_path parameter and insufficient checks in the Local storage backend, enabling an attacker to bypass storage directory restrictions and access sensitive system files (e.g., /etc/passwd) or application configuration files (e.g., settings.py), potentially leading to full system compromise. This vulnerability is fixed in 2.5.1.

Weakness: CWE-73 (External Control of File Name or Path), CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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

It affects 1 product.


Products: Tandoor Recipes.

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

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

## Is CVE-2026-25964 being exploited?

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

Public exploit code:

- CVE-2026-25964 | Tandoor Recipes LFI (github_poc): https://github.com/drkim-dev/CVE-2026-25964

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

What it is: CVE-2026-25964 is a medium-severity path traversal vulnerability in TandoorRecipes recipes, published on 13 Feb 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-25964 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-25964/ (Markdown: https://insights.sbomify.com/CVE-2026-25964/index.md)
```

## Sources

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

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