Mealie household permissions can turn webhooks into network access
Mealie manages recipes, meal plans, shopping lists, households, and groups. A recipe manager may look low risk beside a finance or source-code system. Its notifiers and webhooks are a different matter. The project documentation warns that the Manage household permission lets a user make the server send requests through notifiers and webhooks, and those requests can reach hosts on the internal network. That turns a household-level application role into a network egress decision.
On 2026-11-21, ZoomEye returned 0 matches for app="Mealie" and 4,165 for title="Mealie". The queries used page 1, page size 1, and sub_type=all, from 01:44:10 to 01:44:12 China Standard Time. The counts are index matches, not a claim that a Mealie server is exposed without authentication or that a webhook has reached an internal host. The title result is the useful discovery lead in this measurement.
Separate household management from network authority
Mealie documents permissions such as Administrator, Invite, Manage group, Manage household, and Organize group data. The documentation also describes LDAP and OpenID Connect authentication and customizable public access for non-users. A household member who can create arbitrary webhook destinations should be trusted with more than recipe editing. A team should test whether webhook destinations are restricted to approved hosts, whether redirects are followed, and whether network egress from the Mealie container is limited to the services it needs.
The application-level inventory should record groups, households, users, authentication source, public recipe access, notifier and webhook configuration, and the owner of each integration. The network inventory should record the Mealie workload's outbound path. An internal webhook can reach an administrative panel, a metadata service, or a message broker if the platform has no egress policy. Closing that path is a network control, while limiting the permission is an application control. Both are relevant.
The OIDC configuration is another boundary. Mealie can map identity-provider groups or claims to users and permissions. If a broad group grants household management, the identity provider becomes the effective source of network reach. The review should verify the claim mapping with a test account and confirm that a removed group loses the permission without requiring a manual database edit. Public recipe access should also be reviewed independently from household access.
Test the destination, not only the recipe
A safe review fixture can configure a webhook to a controlled internal test endpoint. The test should show which roles can create, edit, trigger, and delete it. Try a redirect and a disallowed destination in an isolated environment. Confirm that failures produce a useful log without exposing secrets. In production, do not send a test webhook to an unknown service or an internal address that has not been approved.
The 4,165 title matches indicate that product-name discovery can be much broader than a vendor app fingerprint. The zero app result does not remove the title result. Confirm each host through DNS and ownership data, then inspect the authenticated configuration only through an approved administrative process. An internet scan should not attempt to trigger a webhook or retrieve household data.
Mealie's practical risk model is small and concrete: a recipe user with a powerful household permission can cause the server to make an outbound request. The control set is equally concrete: a narrow permission, a destination policy, an egress firewall, logged failures, and a test user who loses access when the group is removed. A recipe application does not need broad network authority by default.
Top comments (0)