KitchenOwl tokens carry household write authority
KitchenOwl tokens carry household write authority KitchenOwl is a self-hosted recipe, shopping-list, meal-plan, and expense application. Its API uses accounts and households. The current documentation describes a regul
KitchenOwl tokens carry household write authority
KitchenOwl is a self-hosted recipe, shopping-list, meal-plan, and expense application. Its API uses accounts and households. The current documentation describes a regular JWT access token and warns that the MCP server token grants full write access to all households the authenticated user belongs to. That warning is the best place to start a deployment review.
A count-only ZoomEye query executed on 2026-11-20 at 04:45 CST used page 1, pagesize 1, and sub_type=all. app="KitchenOwl" returned 0 matches. title="KitchenOwl" returned 396 matches. The title result is a product-name signal, not a count of exposed household data. The application query did not find an exact fingerprint in this run.
KitchenOwl's MCP documentation says the endpoint is disabled by default and can be enabled with KITCHENOWL_MCP_ENABLED=true. It uses the same accounts as the REST API, and requests authenticate with a bearer token. The docs state that every MCP tool is limited to households the authenticated user belongs to, but they also warn that the token has full write access across those households.
Separate login from long-lived access
A browser session and an automation token have different lifetimes and exposure. The documentation says access tokens expire with the refresh-token lifetime, and the default refresh lifetime is 30 days. A client that stores the token on a phone, a desktop, or a home-automation server needs a revocation plan.
Review which clients need read access, which need write access, and which need the MCP endpoint at all. If the MCP server is enabled for an assistant, the assistant can modify lists, recipes, plans, and expenses within the authenticated user's households. Give it a dedicated account only if the application's membership model supports that separation. Do not share a human administrator's token with an automation that does not need administrator actions.
The JWT signing secret is a deployment secret. The docs show a JWT_SECRET_KEY environment value in the example and explicitly recommend changing it. Generate a random value, store it outside the repository, and rotate it when a token compromise requires invalidating sessions. A rotation that also invalidates refresh tokens should be planned and communicated.
Inventory the household boundary
List each household, its members, and the role that controls list and expense changes. Test a user who belongs to one household and confirm that a request for another household fails. Test an expired token and a token from a deleted user. If the deployment offers OIDC, review how an external identity maps to a household invitation and whether an existing email or username can claim the wrong user.
Expose the application through TLS and restrict the management route to the intended network. Backups should include the database and the signing secret only if the backup system is authorized to hold both. A database backup without the signing key may keep data but break sessions; a signing key without the database may let old tokens authenticate against a restored boundary.
The 396 title matches are a lead to verify, not a count of data leaks. The practical review is token scope, household membership, MCP enablement, secret rotation, and session revocation. Those controls determine whether a reachable KitchenOwl instance is a collection of family recipes or a long-lived write path into household operations.
References
Originally published by Dev.to Security. Aggregated on AIWithGhost for educational purposes β full credit and traffic to the original publisher.