The vulnerability is a classic unbounded resource consumption issue. The application's API and Telegram webhook handlers accepted JSON payloads without imposing any limit on the size of the request body. The Go json.Decoder attempts to parse the entire payload, which requires allocating memory for the data structure. An unauthenticated attacker could exploit this by sending a continuous stream of JSON data (e.g., gigabytes of whitespace or padding) in a single request. This forces the application to try and allocate an impossible amount of memory, triggering a fatal runtime: out of memory error, which in turn causes the Linux OOM killer to terminate the process, resulting in a denial of service. The patch addresses this by wrapping the request body with http.MaxBytesReader, which enforces a maximum read size before the JSON decoding begins. The analysis of the commit 0ff87024cb9ed01fc5f5fdc6f4603fce4c123922 clearly shows this mitigation being applied to both the apiHandler and webHandlerTelegramBot functions, confirming they were the points of vulnerability.