CVE-2026-111899
KitchenOwl through 0.7.10 contains a server-side request forgery …
KitchenOwl through 0.7.10 contains a server-side request forgery vulnerability in recipe import that allows authenticated household members to bypass IP filtering via a second unfiltered fetch. Attackers can host a page titled KitchenOwl at a URL matching /recipe/<id>. The follow-up requests.get() call can then be redirected or DNS-rebound to loopback, private-network, or cloud-metadata addresses, exposing internal services.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Set the orderSystems that can be reached from the internet come first, then the rest.
References
- github.com/TomBursch/kitchenowl/blob/v0.7.10/backend/app/service/recipe_scraping.py
- github.com/TomBursch/kitchenowl/commit/292f6f50a8e8bfa487292e9fd0ea0c54a860c28f
- github.com/TomBursch/kitchenowl/issues/1169
- www.vulncheck.com/advisories/kitchenowl-through-0.7.10-ssrf-via-recipe-import-scrapekitche
- nvd.nist.gov/vuln/detail/CVE-2026-111899
- cve.org/CVERecord?id=CVE-2026-111899
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.