Spin can run out of memory if database or web server responses are too large

Monitor vulnerabilities like this one. Sign up free to get alerted when software you use is affected.

6.9

Spin can run out of memory if database or web server responses are too large

CVE-2026-27887

Summary

Spin, a tool for building serverless applications, can crash if it receives extremely large responses from a database or web server. This can happen if a database or server sends a huge amount of data that Spin can't handle. To avoid this, you should only allow Spin to connect to trusted databases and servers that limit their response sizes, or update to a patched version of Spin.

Original title

Original description

Spin is an open source developer tool for building and running serverless applications powered by WebAssembly. When Spin is configured to allow connections to a database or web server which could return responses of unbounded size (e.g. tables with many rows or large content bodies), Spin may in some cases attempt to buffer the entire response before delivering it to the guest, which can lead to the host process running out of memory, panicking, and crashing. In addition, a malicious guest application could incrementally insert a large number of rows or values into a database and then retrieve them all in a single query, leading to large host allocations. Spin 3.6.1, SpinKube 0.6.2, and `containerd-shim-spin` 0.22.1 have been patched to address the issue. As a workaround, configure Spin to only allow access to trusted databases and HTTP servers which limit response sizes.

nvd CVSS4.0 6.9

Vulnerability type

CWE-770 Allocation of Resources Without Limits

CWE-774

CWE-789

https://github.com/spinframework/spin/security/advisories/GHSA-mv4f-6ffm-32wx

Published: 26 Feb 2026 · Updated: 12 Mar 2026 · First seen: 6 Mar 2026