The vulnerability stems from improper error handling in the Language class. The original implementation in formatMessage() threw exceptions for invalid message formats (e.g., malformed ICU message patterns). By repeatedly triggering these exceptions (e.g., via auto-routed requests with crafted parameters), an attacker could exhaust server memory. The commit modifies this method to avoid exceptions, instead logging errors and returning a safe message. The CWE-835 (Infinite Loop) classification aligns with resource exhaustion via repeated error handling, though the exact mechanism is memory consumption rather than CPU-bound loops. The patch's focus on URI validation in Router/Filters and Language class error handling confirms this as the primary vulnerability point.