Kimi CLI's aiohttp server does not enforce a timeout on the initial request or headers, allowing an attacker to keep an idle connection open indefinitely before sending any data. This can lead to resource exhaustion on the server. The vulnerability affects versions 0.40 and later. A recommended workaround is to deploy a reverse proxy with appropriate keepalive timeout settings.