{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-89321 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-89321 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-89321 is a medium-severity denial of service vulnerability in Eclipse OpenVSX, published on 14 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-89321 and fix it if it is affected.\n\nWhat it is: CVE-2026-89321 is a medium-severity denial of service vulnerability in Eclipse OpenVSX, published on 14 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-89321 in the wild and no public exploit code.\n\nAffected product: Eclipse OpenVSX. 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-89321/ (Markdown: https://insights.sbomify.com/CVE-2026-89321/index.md)","id":"CVE-2026-89321","markdown":"https://insights.sbomify.com/CVE-2026-89321/index.md","name":"CVE-2026-89321","record":{"aliases":["GHSA-ggqm-q66x-mqh3","GHSA-h685-gqw7-fqw7"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Eclipse OpenVSX","requires_auth":"low_privilege","summary":"An attacker can upload a highly compressed VSIX to fill the server's temporary filesystem, causing denial of service for file requests.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"eclipse","cpe":[],"cvss":{"score":4.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L","version":"3.1"},"cwes":[{"id":"CWE-409","name":"Improper Handling of Highly Compressed Data (Data Amplification)"}],"description":"Publishing limits the compressed size of a VSIX (ovsx.publishing.max-content-size, 512 MB by default) but nothing limited how large an entry becomes when opened.\n\nOn the first request to /vscode/unpkg/{namespace}/{extension}/{version}/{path}, WebResourceService opened the entry with ZipFile.getInputStream() and passed the decompressed stream to Files.copy(), which ran to the end of the stream without counting bytes written. The result was cached under java.io.tmpdir, and that cache evicted by entry count (150), not by size, so it placed no bound on disk usage.\n\nA publisher with access only to their own namespace could therefore upload a small, highly compressible VSIX and cause the server to write far larger files to the temp filesystem — repeating with different files or versions, since a repeat request is served from the cache.\n\nImpact observed: the temp filesystem filled; requests for files not already cached returned 500 with No space left on device; a failed extraction left a partial cache file that blocked later attempts at that path; publishing failed with Failed to read extension file. Metadata and already-cached files kept working, and the server did not stop.\n\nTriggering the extraction needs no authentication — only the upload does.","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":"Denial of service in Eclipse OpenVSX","id":"CVE-2026-89321","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"Vault ACL Policy Evaluation May Allow Bypass of Deny Restrictions","id":"CVE-2026-89322"},"packages":[],"prev":{"headline":"HmacShaCryptor.Hash never hashes its input — returns constant HMAC_K(\"\") for all inputs, voiding CBC-HMAC JWE integrity","id":"CVE-2026-89320"},"products":["Eclipse OpenVSX"],"published":"2026-09-14","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-09-14","vendors":["Eclipse Foundation"]},"summary":"An attacker can upload a highly compressed VSIX to fill the server's temporary filesystem, causing denial of service for file requests.","url":"https://insights.sbomify.com/CVE-2026-89321/"}