@ai-sdk/provider-utils has an Uncontrolled Resource Consumption issue
CVE-2026-8769 · GHSA-866g-f22w-33x8 · published 2026-05-18 · updated 2026-09-08
- Severity
- Low
- CVSS score
- 4.3
- Chance of exploitation (EPSS)
- 0.56%
- Fixed in
- 5.0.1
- Exploitation Public proof of concept
- Automatable No
- Technical impact Partial
- CISA SSVC
Versions of @ai-sdk/provider-utils before 3.0.28, from 4.0.0 before 4.0.33, and from 5.0.0 before 5.0.1 are vulnerable to uncontrolled resource consumption. The createJsonResponseHandler, createJsonErrorResponseHandler, and createStatusCodeErrorResponseHandler functions in read response bodies without a shared size limit, allowing a remote attacker with low privileges to cause excessive memory consumption. The exploit has been publicly disclosed and may be utilized.
Upgrade @ai-sdk/provider-utils to 5.0.1 or later.
| Package | Registry | Affected | Fixed in |
|---|---|---|---|
| @ai-sdk/provider-utils | npm | < 3.0.28 | 3.0.28 |
| @ai-sdk/provider-utils | npm | >= 4.0.0-beta.10, < 4.0.33 | 4.0.33 |
| @ai-sdk/provider-utils | npm | >= 5.0.0-beta.0, < 5.0.1 | 5.0.1 |
- HightsParticles: Unbounded HTTP Request Body Buffering in @tsparticles/mcp-server Leads to Remote DoS@tsparticles/mcp-server
- HighMissing request-wide media budget allows single-request frontend resource exhaustionvllm
- HighMCP TypeScript SDK: HTTP server transports and handlers did not limit request body size or JSON-RPC batch length@modelcontextprotocol/hono, @modelcontextprotocol/node, @modelcontextprotocol/sdk, @modelcontextprotocol/server
- HighvLLM : DoS via unvalidated mm_processor_kwargs in multimodal image processors (Isaac, InternVL, H2OVL, etc.)vllm
- HighMCP TypeScript SDK: One HTTP request within the default size limit could exhaust server memory during validation@modelcontextprotocol/sdk, @modelcontextprotocol/server
- HighFrame-count cap bypass in VideoMediaIO.load_base64 for video/jpeg via media_io_kwargs.video.num_framesvllm
The impact, patch and workaround text comes from the advisory, shortened (GitHub Advisory Database, CC BY 4.0). Proof-of-concept and reproduction sections and code are left out; the original advisory has them.