CVE-2026-115810 in Tandoor Recipes
Summary
by MITRE • 10/23/2026
Tandoor Recipes before 2.7.0 contains a server-side request forgery vulnerability in the Pestle importer that allows authenticated low-privileged users to force the server to issue GET requests to arbitrary internal or external hosts by crafting a malicious image URL in a Pestle JSON import file. Attackers can exploit the raw requests.get call in cookbook/integration/pestle.py, which bypasses the application's centralized requests-hardened SSRF filter, to reach internal-only endpoints, perform port/service discovery, and exfiltrate internal responses via the stored recipe image.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Analysis
by VulDB Data Team • 10/23/2026
The vulnerability identified in Tandoor Recipes prior to version 2.7.0 represents a critical server-side request forgery flaw located within the Pestle importer module. This security defect allows authenticated users with low-privileged access levels to manipulate the application into making HTTP requests to arbitrary destinations, including internal network resources and external hosts under attacker control. The exploitation vector relies on crafting a malicious image URL within a JSON import file formatted for the Pestle specification. When the system processes this imported data, it attempts to fetch or validate the provided image source without adequate restrictions, thereby triggering an outbound connection from the server itself rather than the client browser.
The technical root cause of this vulnerability lies in the specific implementation details of the cookbook/integration/pestle.py module. The code utilizes a raw requests.get call that operates independently of the application's centralized security controls. Tandoor Recipes employs a hardened SSRF filter designed to mitigate such attacks by validating and restricting outbound connections based on predefined allowlists or blocklists. However, because this particular import function bypasses that central filtering mechanism, it effectively creates an unfiltered pathway for network requests. This architectural oversight means that the robust security measures intended to protect against server-side request forgery are rendered ineffective when triggered through this specific code path.
The operational impact of exploiting this vulnerability is significant and multifaceted. An attacker can leverage this flaw to perform reconnaissance activities within the internal network, such as port scanning and service discovery on hosts that are not directly accessible from the internet. By directing the server to probe various IP addresses and ports, an adversary can map out the internal infrastructure, identifying running services, open ports, and potentially vulnerable systems. Furthermore, if the application returns error messages or content related to the requested resource in its response, it may lead to information disclosure through blind SSRF techniques where data is exfiltrated via side channels such as HTTP status codes, timing differences, or stored responses within recipe images.
This vulnerability aligns with Common Weakness Enumeration identifier CWE-918, which describes Server-Side Request Forgery (SSRF). The attack pattern corresponds to MITRE ATT&CK technique T1571, specifically the Non-Standard Port variant if internal services are accessed on non-standard ports, or generally falls under network reconnaissance and data exfiltration tactics. The ability of a low-privileged user to execute these actions highlights a failure in access control logic regarding resource validation functions that involve external interactions.
To mitigate this vulnerability, it is imperative to upgrade Tandoor Recipes to version 2.7.0 or later, where the code path has been corrected to enforce proper SSRF protections. In environments where immediate patching is not feasible, administrators should implement network-level controls such as firewall rules that restrict outbound HTTP and HTTPS traffic from the application server to only known necessary destinations. Additionally, deploying a web application firewall with specific signatures for SSRF detection can provide an additional layer of defense by blocking requests targeting private IP ranges or suspicious external domains. Input validation on all import fields should also be strengthened to ensure that URLs are strictly validated against an allowlist before being processed by any request library.