On a multi-user Mealie instance, any registered user could create an event notifier pointing at their own URL and then move it into another group or household. From then on, that household's recipe changes, shopping-list changes and meal-plan entries were sent to the attacker, with no action by the victim.
The problem
When a notifier is created, Mealie sets its group_id and household_id to the caller's own. When it is updated, it did not: the update body carried both fields, and the generic update wrote them to the row as given. The row lookup was limited to the caller's household, so the caller could only update their own notifier, but the update could move it into any other household. Events in that household are delivered to every notifier stored under it, including the moved one.
The only thing the attacker needs is the victim's group and household IDs, which appear in public recipe data. The same update path carried the tenant fields for recipe actions, shopping lists, cookbooks and labels, so the report suggested refusing changes to those fields at the update layer rather than per endpoint.
How it was shown
The path was traced through the source of version 3.29.0: the create handler fixes the tenant fields, the update handler does not, the update schema accepts both as client input, the generic repository update writes them, and the event listener selects notifiers by the household's IDs. It was reported through GitHub's private vulnerability reporting.
Response
The maintainer accepted the report and fixed the class in pull request #8965, "keep updates from moving rows to another group or household". The fix shipped in Mealie 3.31.0 (13 Nov 2026), whose release notes list a batch of fixes for data access between groups and households. The advisory GHSA-qwhr-6537-wj7f was published the same day, rated Moderate (CWE-639, CWE-915), with the report credited. A CVE has been requested.
Links
Cite as
Nobuo Otoi (ba-cybersecurity.com). Mealie: a notifier could be moved into another household by mass assignment on update (report and fix). 2026. https://ba-cybersecurity.com/research/mealie-notifier-reassignment/.
@misc{otoi2026mealie,
author = {Otoi, Nobuo},
title = {Mealie: a notifier could be moved into another household by mass assignment on update (report and fix)},
year = {2026},
howpublished = {\url{https://ba-cybersecurity.com/research/mealie-notifier-reassignment/}},
note = {Advisory: GHSA-qwhr-6537-wj7f - Fix: https://github.com/mealie-recipes/mealie/pull/8965}
}
Reported 24 Oct 2026 - Fixed and released 13 Nov 2026 (3.31.0) · This page: updated 15 Nov 2026 · Permanent address: https://ba-cybersecurity.com/research/mealie-notifier-reassignment/