Recipes server-side request forgery in Nextcloud storage
Only affects Tandoor Recipes before 2.7.4 with the Nextcloud storage provider, where the attacker must be a space admin who can create a Nextcloud storage. Fixed in 2.7.4.
- Exploited
- Proof of concept public, per CISA
- Fix
- Fixed in 2.7.4
- Who is exposed
- Specific setups only
Summary
Tandoor Recipes has a server-side request forgery flaw in its Nextcloud storage handling, which a remote attacker can reach over the network after logging in with low privileges. By pointing a Nextcloud storage at internal hosts and importing a file through it, the attacker can read responses from internal services or cloud metadata endpoints.
Written by a model
Original description
Tandoor Recipes before 2.7.4 contains a server-side request forgery vulnerability that allows space admins to reach internal hosts because Nextcloud.get_client builds WebDAV clients from Storage.url without calling safe_request. Attackers can create a NEXTCLOUD storage via POST /api/storage/ pointing at internal hosts, import a file, then call GET /api/get_recipe_file/<id>/ to read internal service or cloud metadata responses.
Who should check
Teams running Tandoor Recipes before 2.7.4 with Nextcloud storage, especially multi-tenant hosts where users self-register as space admins
“Affecting recipes >= 0, < 2.7.4”
What to do
Check whether your setup matches what the bug needs.
Tandoor Recipes before 2.7.4 with the Nextcloud storage provider Attacker must be a space admin who can create a NEXTCLOUD storageUpgrade to a fixed version: 2.7.4.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-133235 (Tandoor Recipes before 2.7.4 SSRF via Nextcloud Storage WebDAV Client), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-133235 (entry last updated 2026-11-19):
Affected:
- TandoorRecipes recipes: fixed in 2.7.4
Fixed versions: 2.7.4.
Conditions (all must be true for the bug to be hit):
- Tandoor Recipes before 2.7.4 with the Nextcloud storage provider (source: https://github.com/TandoorRecipes/recipes/security/advisories/GHSA-qgw5-hm36-x26x)
- Attacker must be a space admin who can create a NEXTCLOUD storage (source: https://www.vulncheck.com/advisories/tandoor-recipes-before-2.7.4-ssrf-via-nextcloud-storage-webdav-client)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-133235 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-133235 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/TandoorRecipes/recipes/security/advisories/GHSA-qgw5-hm36-x26x
- https://github.com/TandoorRecipes/recipes/commit/fd7fbe4d61cf18623a77104018f5352702a2bb76
- https://github.com/TandoorRecipes/recipes/releases/tag/2.7.4
- https://github.com/TandoorRecipes/recipes/blob/2.7.2/cookbook/provider/nextcloud.py#L17-L27
- https://github.com/TandoorRecipes/recipes
- https://www.vulncheck.com/advisories/tandoor-recipes-before-2.7.4-ssrf-via-nextcloud-storage-webdav-client
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-133235
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-133235"}.Affected versions
- TandoorRecipes recipesfixed in 2.7.4
cve.now Index
- Exploitation15/40CISA rates a proof of concept as public
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Unknown. No tracked technology or package matched
- Severity8.3/10CVSS 8.3
- No patch0/5No signal
What would change the score
- Would score about 66 if added to CISA KEV
- Would score about 61 if CISA's SSVC rates exploitation active
- Would score about 38 if CISA's SSVC rates it automatable
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: poc · Automatable: no · Technical impact: partial
- Record last updated
Evidence 9
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | GitHub · TandoorRecipes/recipes · Advisory GHSA-qgw5-hm36-x26x |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-133235 |
| Record | NVD · CVE-2026-133235 |
| Public exploit code 1Establishes: Public exploit code exists (Exploit-DB, Metasploit, Nuclei and GitHub). | |
| Exploit | GitHub · LLCForge/CVE-2026-133235 · Repository |
| Other links 5 | |
| Patch | GitHub · TandoorRecipes/recipes · Commit fd7fbe4d |
| Repository | GitHub · TandoorRecipes/recipes · Release 2.7.4 |
| Repository | GitHub · TandoorRecipes/recipes · cookbook/provider/nextcloud.py · L17-L27 |
| Repository | GitHub · TandoorRecipes/recipes · Repository |
| Link | vulncheck.com · advisories/tandoor-recipes-before-2.7.4-ssrf-via-nextcloud-storage-webdav-client |
Questions about CVE-2026-133235
Is CVE-2026-133235 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. CISA's SSVC assessment notes a proof of concept exists. No public exploit code is tracked.
Source: cve.now feed data
What does this mean?
The Nextcloud storage provider's WebDAV client is pointed at a user-supplied storage URL without restriction, so a space admin can make the server send requests to internal hosts or cloud metadata endpoints. The response bodies can then be read back as a file download through the recipe file endpoint.
Source: github.com, vulncheck.com
Which versions are affected by CVE-2026-133235?
recipes: before 2.7.4.
Source: cve.now feed data
Am I affected, and how do I check?
Tandoor Recipes versions before 2.7.4 are affected when the Nextcloud storage provider is in use. To check, look at the installed version and whether a Nextcloud storage is configured for a space.
Source: github.com, vulncheck.com
How do I fix CVE-2026-133235?
Upgrade Tandoor Recipes to version 2.7.4 or later, which contains the fix.
Source: github.com, vulncheck.com
Related
- CVE-2026-33152Tandoor Recipes Vulnerable to Unrestricted Brute-Force via BasicAuthentication
- CVE-2026-61726Tandoor Recipes: Private recipe authorization bypass via /api/step/ - read and modify another Space member's private recipe content
- CVE-2026-35488Tandoor Recipes — CustomIsShared permits DELETE/PUT on RecipeBook by shared (read-only) users
- CVE-2026-35045Tandoor Recipes Affected by Private Recipe Exposure and Unauthorized Modification
- CVE-2026-33149Tandoor Recipes Vulnerable to Host Header Injection
- CVE-2026-59970Tandoor Recipes: Blind SSRF via AI provider URL (api_base)
No corrections so far. Something wrong on this page? Report an error.