{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-27887 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-27887 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-27887 is a medium-severity denial of service vulnerability in spinframework SpinKube, published on 26 Feb 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-27887 and fix it if it is affected.\n\nWhat it is: CVE-2026-27887 is a medium-severity denial of service vulnerability in spinframework SpinKube, published on 26 Feb 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-27887 in the wild and no public exploit code.\n\nAffected product: spinframework SpinKube. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-27887/ (Markdown: https://insights.sbomify.com/CVE-2026-27887/index.md)","id":"CVE-2026-27887","markdown":"https://insights.sbomify.com/CVE-2026-27887/index.md","name":"CVE-2026-27887","record":{"aliases":["GHSA-mv4f-6ffm-32wx"],"analysis":{"component_type":"developer_tool","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"WebAssembly serverless tool","requires_auth":"low_privilege","summary":"Attackers can cause Spin host crashes via memory exhaustion by triggering unbounded database or web server responses.","user_interaction":"required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":6.9,"severity":"medium","source":"cna","vector":"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","version":"4.0"},"cwes":[{"id":"CWE-789","name":"Memory Allocation with Excessive Size Value"},{"id":"CWE-774","name":"Allocation of File Descriptors or Handles Without Limits or Throttling"},{"id":"CWE-770","name":"Allocation of Resources Without Limits or Throttling"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Spin has memory leaks in various WIT interfaces","id":"CVE-2026-27887","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"pypdf: Manipulated FlateDecode XFA streams can exhaust RAM","id":"CVE-2026-27888"},"packages":[],"prev":{"headline":"Strapi may leak sensitive data via relational filtering due to lack of query sanitization","id":"CVE-2026-27886"},"products":["SpinKube","containerd-shim-spin","spin"],"published":"2026-02-26","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-02-26","vendors":["spinframework"]},"summary":"Attackers can cause Spin host crashes via memory exhaustion by triggering unbounded database or web server responses.","url":"https://insights.sbomify.com/CVE-2026-27887/"}