Back Redpacketsecurity CVE Alert: CVE-2026-115810 – TandoorRecipes
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.
**Risk verdict:** Prioritise remediation for internet-reachable deployments, but active exploitation cannot be confirmed because KEV, SSVC, PoC and EPSS data were not provided.
**Why this matters:** An attacker with a basic account could use the application server as a route into otherwise inaccessible network services. The main concern is exposure of internal information, including credentials or cloud service data, rather than direct changes to recipes or service disruption.
**Most likely attack path:** The attack is network-reachable, needs low privileges and little effort, and requires no further user action. A malicious Pestle import can make the server attacker-selected destinations; the affected flow can bypass the application’s usual SSRF protections. The changed scope means impact may extend to internal systems reachable from the server.
**Who is most exposed:** Self-hosted instances, especially those reachable from the public internet and permitted to connect to private networks or cloud metadata services, warrant the closest attention. Shared installations also increase the number of accounts that could be used to attempt exploitation.
Review import activity and application logs for Pestle imports followed by unusual outbound requests.
Check proxy, DNS and firewall logs for connections from the application host to private, link-local or unexpected destinations.
Look for unexpected recipe image files or image retrievals associated with recent imports.
Investigate outbound requests to internal administration or metadata endpoints.
Mitigation and prioritisation
Upgrade to the vendor’s fixed release; expedite for exposed instances.
Restrict application egress to required destinations and block access to metadata and sensitive internal services.
Review recent imports and investigate suspicious server-side requests.
Test the update in staging, then deploy through normal change controls without delaying urgent internet-facing remediation.
A considerable amount of time and effort goes into maintaining this website, creating backend automation and creating new features and content for you to make actionable intelligence decisions. Everyone that supports the site helps enable new functionality.
If you like the site, please support us on Patreon or Buy Me A Coffee using the buttons below.
The full story
This article is one source in a clustered incident — the cluster page carries the summary, timeline and every other outlet covering it.
