---
id: "CVE-2026-111899"
kind: "vulnerability"
aliases: ["CVE-2026-111899"]
title: "KitchenOwl: recipe import lets logged-in users reach internal addresses"
severity: "medium"
cvss: 5.3
epss: null
exploited: false
status: "open"
category: "package"
products: []
ecosystems: []
tags: ["cloud-hosted", "kitchenowl", "package", "self-hosted"]
not_affected_if: ["auth-required", "no-url-recipe-import"]
published_at: "2026-10-19T14:17:00+00:00"
first_seen_at: "2026-10-23T21:57:18+00:00"
updated_at: "2026-10-25T04:25:10+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-111899", "first_seen_at": "2026-10-23T21:57:18+00:00"}]
---

# KitchenOwl: recipe import lets logged-in users reach internal addresses

KitchenOwl's recipe import fetches a second URL without the IP filter applied to the first request, so a crafted page can redirect or DNS-rebind the server to loopback, private-network or cloud-metadata addresses. An authenticated household member can use this to read internal services.

_Summary, check and fix written by a model from the sources; labelled as such._

## How to check

- Check the installed KitchenOwl version with the deployment's image tag or package version, and compare it against `0.7.10`.
- Confirm whether recipe import from URLs is in use on the instance.

## Fix

- Upgrade KitchenOwl past `0.7.10` once a fixed release is published; the sources do not name the fixed version.
- Until then, restrict outbound network access from the KitchenOwl server to metadata and internal ranges.

## Timeline

- 2026-10-23T21:57:18+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-111899

## From the sources

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.

---

_Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_