VulnerabilityPublished 26 Mar 2026

CVE-2026-33148: TandoorRecipes recipes · Injection

Affects TandoorRecipes recipesSource CVE Database V5

Compare

Not known to be exploited · CVSS 6.5 Medium : upgrade to 2.6.0 when convenient.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 3.1 base score

6.5Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.4% chance of exploitation in 30 days – higher than 41% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 2.6.0

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: None
Availability: High

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 26 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade recipes and tandoorrecipes/recipes to 2.6.0.

Affected software

Product	Affected	Fixed in
TandoorRecipesrecipes	Affected <2.6.0	Fixed in 2.6.0
GitHubtandoorrecipes/recipes`pkg:github/tandoorrecipes/recipes`Other threats	Affected <2.6.0	Fixed in 2.6.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Organizations should upgrade Tandoor Recipes to version 2.6.0 or later, where the vulnerability is patched. Until upgrading is possible, implement strict input validation and sanitization on the 'query' parameter to ensure it does not contain special characters such as '&' that could alter URL construction. Employ URL encoding on all user-supplied input before embedding it into URLs to prevent injection of additional parameters. Monitor application logs for unusual upstream API request patterns or HTTP 500 errors that may indicate exploitation attempts. Limit privileges of users who can submit queries to reduce the risk of exploitation. Additionally, consider implementing rate limiting on the FDC search endpoint to mitigate denial of service attempts. Review and restrict API key usage policies with the upstream USDA FoodData Central service to detect and prevent unauthorized key overrides or abuse. Conduct regular security assessments and code reviews focusing on input handling and output encoding to prevent similar injection vulnerabilities.

Description

Tandoor Recipes is an application for managing recipes, planning meals, and building shopping lists. In versions prior to 2.6.0, the FDC (USDA FoodData Central) search endpoint constructs an upstream API URL by directly interpolating the user-supplied `query` parameter into the URL string without URL-encoding. An attacker can inject additional URL parameters by including `&` characters in the query value. This allows overriding the API key, manipulating upstream query behavior, and causing server crashes (HTTP 500) via malformed requests — a Denial of Service condition. Version 2.6.0 patches the issue.

Impact

This vulnerability primarily impacts the availability of the Tandoor Recipes service by enabling denial of service through server crashes triggered by malformed upstream API requests. Attackers can disrupt meal planning and recipe management functionalities for users relying on the application, potentially affecting business continuity for organizations that integrate Tandoor Recipes into their workflows. Additionally, the ability to override the API key parameter could lead to unauthorized use or abuse of the upstream USDA FoodData Central API quota or data, potentially causing service disruptions or additional costs. While confidentiality and integrity are not directly affected, the disruption of service can degrade user trust and operational efficiency. Organizations using affected versions may face increased support costs and reputational damage if the service becomes unreliable. The medium severity rating reflects the moderate impact and relatively low complexity of exploitation, emphasizing the need for timely remediation.

CWE-74Improper Neutralization of Special Elements in Output Used by a Downstream Component (Injection) (opens in a new tab)
Class weaknessLikelihood of exploit: HighOWASP Top 10 A05:2025: Injection (opens in a new tab)
The product constructs all or part of a command, data structure, or record using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify how it is parsed or interpreted when it is sent to a downstream component.
MITRE discourages mapping vulnerabilities to this broad entry; the root cause is usually a more specific weakness.
Requirements
Programming languages and supporting technologies might be chosen which are not subject to these issues.
Implementation
Utilize an appropriate mix of allowlist and denylist parsing to filter control-plane syntax from all input.
OWASP Cheat Sheets
Abuse Case (opens in a new tab)
Deserialization (opens in a new tab)
Injection Prevention (opens in a new tab)
SQL Injection Prevention (opens in a new tab)
Injection Prevention in Java (opens in a new tab)
OWASP ASVS 4.0.3
V1.5.1 (opens in a new tab)
Attack patterns
Buffer Overflow via Environment Variables (opens in a new tab)
Server Side Include (SSI) Injection (opens in a new tab)
HTTP Request Splitting (opens in a new tab)
Command Line Execution through SQL Injection (opens in a new tab)
Double Encoding (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

github.com/TandoorRecipes/recipes/security/advisories/GHSA-43p3-wx6h-9g7w (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 26 Mar 2026, 19:46 UTC

WeaknessesCWE-74

Technical details

References

Community reviews

Related threats