Description

A weakness has been identified in mealie-recipes Mealie up to 3.25.1. Affected is the function payload.model_dump of the file mealie/routes/households/controller_group_recipe_actions.py of the component Recipe Action Trigger. Executing a manipulation of the argument url can lead to server-side request forgery. The attack can be executed remotely. The exploit has been made available to the public and could be used for attacks. Upgrading to version 3.26.0 is able to address this issue. This patch is called fb221afa258c8dd2c4ac95b1996c33ef9db3f477. The affected component should be upgraded.

Executive Summary

Technical Details

Mitigations

References

Additional Metadata

{
  "score": "4.3",
  "pubDate": "2026-09-20T13:17:46.903Z",
  "pubdate": "2026-09-20T13:17:46.903Z",
  "executiveSummary": "A Server-Side Request Forgery (SSRF) vulnerability exists in Mealie versions up to 3.25.1. The flaw is located within the Recipe Action Trigger component, specifically in the payload.model_dump function found in mealie/routes/households/controller_group_recipe_actions.py.\nThe vulnerability allows a remote, unauthenticated, or authenticated attacker (depending on deployment configuration) to manipulate the 'url' argument passed to the application. This manipulation enables the server to initiate unauthorized outbound requests to arbitrary destinations, including internal network resources or local services.\nThe risk is significant as it facilitates unauthorized interactions with backend infrastructure, potentially leading to information disclosure, port scanning of internal networks, or the exploitation of other internal services that lack robust authentication. The vulnerability is confirmed as publicly exploitable, increasing the risk of active exploitation. Immediate remediation by updating the software to version 3.26.0 is required.",
  "technicalDetails": "The vulnerability originates from improper input validation within the Recipe Action Trigger component of Mealie. Specifically, the function payload.model_dump in mealie/routes/households/controller_group_recipe_actions.py fails to sanitize or restrict the 'url' parameter provided by the user.\nIn a standard execution flow, the Mealie application processes recipe actions that involve external resource retrieval. When a user submits a crafted payload containing a malicious URL, the application passes this data into the backend processing logic without verifying the destination host or protocol. This allows an attacker to control the target of the HTTP requests performed by the server.\nExploitation involves injecting a controlled URI into the 'url' argument. When the application processes this input, the server-side logic executes a request to the specified resource. By targeting internal IP addresses (e.g., 127.0.0.1, 169.254.169.254, or private RFC1918 subnets) or non-standard ports, an attacker can bypass traditional perimeter firewalls. This allows the attacker to reach services hosted within the same environment as the Mealie instance that are not intended to be exposed to the public internet.\nThe impact of this SSRF is severe. Beyond simple resource retrieval, an attacker may be able to interact with internal APIs, perform reconnaissance on the internal network topology, or extract sensitive metadata from cloud environments if the service is deployed within such an infrastructure. Since the request originates from the trusted Mealie server, many internal services may treat the incoming request as inherently authorized, leading to unauthorized state changes or data leakage.\nThe vulnerability affects versions up to 3.25.1. The provided patch, identified as commit fb221afa258c8dd2c4ac95b1996c33ef9db3f477, introduces the necessary validation logic to restrict the allowed URLs or destinations, effectively neutralizing the injection vector. Because the exploit is currently publicly available, the attack surface is considered highly exposed to automated scanning and manual exploitation efforts."
}