Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2026-25991: CWE-918: Server-Side Request Forgery (SSRF) in TandoorRecipes recipes

0
High
VulnerabilityCVE-2026-25991cvecve-2026-25991cwe-918
Published: Fri Feb 13 2026 (02/13/2026, 18:29:10 UTC)
Source: CVE Database V5
Vendor/Project: TandoorRecipes
Product: recipes

Description

CVE-2026-25991 is a high-severity Server-Side Request Forgery (SSRF) vulnerability affecting Tandoor Recipes versions prior to 2. 5. 1. It exists in the Cookmate recipe import feature, where the application fails to properly validate destination URLs after HTTP redirects. This allows any authenticated user, including those without administrative privileges, to coerce the server into making arbitrary HTTP requests to internal or external resources. Exploitation can lead to internal network scanning, unauthorized access to cloud metadata services (such as AWS or GCP), and disclosure of the server's real IP address. The vulnerability is fixed in version 2. 5. 1. No known exploits are currently reported in the wild.

AI-Powered Analysis

AILast updated: 02/13/2026, 19:03:45 UTC

Technical Analysis

CVE-2026-25991 is a Blind Server-Side Request Forgery (SSRF) vulnerability identified in the Cookmate integration component of Tandoor Recipes, an application used for recipe management and meal planning. The flaw resides in the handling of URLs during the recipe import process, specifically in the cookbook/integration/cookmate.py file. When a user imports recipes via the Cookmate feature, the application follows HTTP redirects but fails to validate the final destination URL properly. This oversight enables any authenticated user, including those with standard user privileges, to manipulate the server into sending HTTP requests to arbitrary destinations. Because the server acts as a proxy, attackers can scan internal network ports, potentially discovering sensitive services not exposed externally. Additionally, attackers can query cloud provider metadata endpoints (e.g., AWS EC2 or Google Cloud metadata services), which often contain sensitive information like instance credentials or configuration data. The vulnerability does not require administrative privileges or user interaction beyond authentication, increasing its risk. The CVSS v3.1 score is 7.7 (high), reflecting the vulnerability's ability to compromise confidentiality without impacting integrity or availability. The vulnerability was publicly disclosed on February 13, 2026, and is resolved in Tandoor Recipes version 2.5.1. No public exploit code or active exploitation has been reported to date.

Potential Impact

For European organizations using Tandoor Recipes versions prior to 2.5.1, this SSRF vulnerability poses significant risks. Attackers with valid user credentials can leverage the flaw to perform internal reconnaissance, potentially identifying vulnerable internal services or misconfigurations. Access to cloud metadata services could lead to credential theft, enabling further lateral movement or data exfiltration. Disclosure of the server's real IP address may facilitate targeted attacks or bypass network protections. Given the application's use in meal planning and recipe management, organizations in hospitality, food services, or related sectors may be affected. The breach of confidentiality could expose sensitive business information or user data. While the vulnerability does not directly affect system integrity or availability, the indirect consequences of credential compromise or network mapping could lead to more severe attacks. The impact is heightened in cloud-hosted environments common in Europe, where metadata services are critical for instance management.

Mitigation Recommendations

European organizations should immediately upgrade Tandoor Recipes to version 2.5.1 or later to apply the official patch addressing this SSRF vulnerability. Until the upgrade is possible, restrict access to the Cookmate import feature to trusted users only and monitor usage logs for suspicious activity. Implement network-level controls to limit outbound HTTP requests from the application server, especially to internal IP ranges and cloud metadata endpoints (e.g., block access to 169.254.169.254). Employ web application firewalls (WAFs) with rules designed to detect and block SSRF patterns, particularly those involving redirect chains or unusual URL parameters. Enforce the principle of least privilege for user accounts, ensuring that only necessary users have authentication access to the application. Conduct internal network segmentation to reduce the impact of potential SSRF exploitation. Regularly audit and monitor cloud metadata service access logs for anomalous queries. Finally, educate developers and administrators on secure URL validation and redirect handling to prevent similar vulnerabilities in future.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
GitHub_M
Date Reserved
2026-02-09T17:41:55.858Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 698f723cc9e1ff5ad857abd9

Added to database: 2/13/2026, 6:49:32 PM

Last enriched: 2/13/2026, 7:03:45 PM

Last updated: 2/13/2026, 8:00:32 PM

Views: 4

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats