CVE-2025-56795

Mealie 3.26.0 through 3.28.0 contains a server-side request forgery vulnerability in the OpenID Connect avatar fetch that ignores ports when allowlisting the identity provider hostname. Authenticated OIDC users who control their picture URL can make the server send GET requests to arbitrary ports on the provider's internal address on each login.

A weakness was identified in mealie-recipes Mealie up to 3.25.1 in the function payload.model_dump of the file mealie/routes/households/controller_group_recipe_actions.py of the Recipe Action Trigger component. Manipulation of the argument url leads to server-side request forgery. The attack can be executed remotely and the exploit is publicly available.

Mealie before version 3.21.0 fails to validate user ownership in the ratings and favorites endpoints, allowing authenticated attackers to read any user's recipe ratings and favorites by specifying arbitrary user IDs in the URL path. Attackers can access private recipe identifiers, rating values, and favorite flags belonging to other users.

Mealie's AsyncSafeTransport SSRF guard (mealie/pkgs/safehttp/transport.py) resolves a target hostname once, checks the resolved IP against private-range rules, but then issues the actual outbound HTTP request using the original hostname, which the underlying async transport re-resolves independently.

The vulnerability in Mealie 1.0.0beta3 fails to terminate download tokens after a user logs out, allowing attackers to perform a man-in-the-middle attack via a crafted GET request.