dbcve.org
Resource Allocation Without LimitsWeakness · CWE-770

CVE-2026-27887

MEDIUM · 6.9 CVSS v4.0 Published 2026-02-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
73/100
Remediation priority · Elevated
Remotely reachable

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Spin, a serverless WebAssembly tool, fails to limit response sizes when connecting to databases or HTTP servers. The host buffers entire responses in memory before delivering them to guest applications, causing memory exhaustion, panic, and crash. Additionally, a malicious guest can trigger large allocations by inserting many rows and retrieving them all at once.

MitigationUpgrade to Spin 3.6.1, SpinKube 0.6.2, or containerd-shim-spin 0.22.1. As a workaround or additional hardening, configure Spin to only connect to trusted databases and HTTP servers that enforce response size limits.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
Authentication
X
User interaction
P
Scope
X

CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:P/VC:N/VI:N/VA:H/SC:N/SI:N/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Spin version
    Run 'spin --version' or check the version of the spin package in your deployment (container image tag, Helm chart version, or binary version)
    Affected if Version is below 3.6.1 for standalone Spin, below 0.6.2 for SpinKube, or below 0.22.1 for containerd-shim-spin
  2. Check if Spin connects to external databases
    Review Spin application manifests (spin.toml) and runtime configuration for any 'sqlite' or database connection definitions that fetch unbounded query results
    Affected if Spin is configured to query databases without external response size limits enforced by the database itself
  3. Check if Spin makes outbound HTTP requests
    Review spin.toml for HTTP outgoing handlers or examine network policies that allow Spin to connect to arbitrary HTTP endpoints
    Affected if Spin guest applications can make HTTP requests to untrusted or uncontrolled external servers returning large responses
  4. Monitor for memory exhaustion symptoms
    Check Spin host logs, system dmesg, or container runtime logs for out-of-memory errors, panics, or crashes that coincide with database queries or HTTP responses
    Affected if Memory exhaustion or process crashes occur after handling large database result sets or HTTP response bodies
  5. Verify workload isolation boundaries
    Confirm whether multiple guest WebAssembly modules share the same Spin host process and can trigger large allocations on each other's behalf
    Affected if Untrusted guest Wasm modules can cause memory pressure affecting the entire Spin host

You are affected if running a Spin version below 3.6.1 (or SpinKube below 0.6.2, or containerd-shim-spin below 0.22.1) AND your Spin applications connect to external databases or HTTP servers that can return arbitrarily large responses.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to Spin 3.6.1, SpinKube 0.6.2, or containerd-shim-spin 0.22.1. As a workaround or additional hardening, configure Spin to only connect to trusted databases and HTTP servers that enforce response size limits.

Recommended fix High confidence

Spin 3.6.1, SpinKube 0.6.2, containerd-shim-spin 0.22.1 (or later)

  1. Upgrade Spin to version 3.6.1 or later
  2. Upgrade SpinKube to version 0.6.2 or later
  3. Upgrade containerd-shim-spin to version 0.22.1 or later

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
14.0 hours of engineering $2,480
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,968.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-27887 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-27887 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data