{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-13323 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-13323 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-13323 is a medium-severity cross-site scripting vulnerability in Eclipse Open VSX, published on 1 Jul 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-13323 and fix it if it is affected.\n\nWhat it is: CVE-2026-13323 is a medium-severity cross-site scripting vulnerability in Eclipse Open VSX, published on 1 Jul 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-13323 in the wild and no public exploit code.\n\nAffected product: Eclipse Open VSX. 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-13323/ (Markdown: https://insights.sbomify.com/CVE-2026-13323/index.md)","id":"CVE-2026-13323","markdown":"https://insights.sbomify.com/CVE-2026-13323/index.md","name":"CVE-2026-13323","record":{"aliases":["GHSA-f3mc-x4vf-jrw2"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["account_takeover","code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Open VSX Registry","requires_auth":"low_privilege","summary":"An attacker can inject HTML into the registry to steal tokens and publish malicious extensions, compromising downstream editor users.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"eclipse","cpe":[{"product":"open_vsx","vendor":"eclipse"}],"cvss":{"score":4.1,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"In Open VSX Registry before 1.0.2, the /vscode/unpkg/ endpoint serves user-supplied HTML files with Content-Type: text/html and without a Content-Security-Policy or Content-Disposition: attachment response header. An unauthenticated attacker can register a publisher account, upload a VSIX containing a crafted HTML payload, and induce an authenticated user to visit the resulting URL. The browser renders the file inline in the open-vsx.org origin context, enabling session token exfiltration, persistent Personal Access Token (PAT) generation, and unauthorized publication of malicious extension versions. Because Open VSX extensions are distributed to VS Code, VSCodium, Cursor, Windsurf, and compatible editors, a compromised extension update constitutes a supply chain attack against all downstream users.","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":"Cross-site scripting in Eclipse Open VSX","id":"CVE-2026-13323","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"Red Hat Product Security has come to the conclusion that this CVE is not needed.","id":"CVE-2026-13325"},"packages":[],"prev":{"headline":"Kubevirt: virt-handler-rhel9: kubevirt: unbounded virtio-serial readline in virt-handler causes oom denial of service","id":"CVE-2026-13322"},"products":["Eclipse Open VSX"],"published":"2026-07-01","related":[{"cvss_score":7.6,"headline":"Privilege escalation in Eclipse Open VSX Registry","id":"CVE-2025-6705","kev_date_added":null,"published":"2025-06-27"},{"cvss_score":6.9,"headline":"Improper Authorization in /user/namespace/{namespace}/details","id":"CVE-2025-1007","kev_date_added":null,"published":"2025-02-19"},{"cvss_score":4.1,"headline":"Cross-site scripting in Eclipse Open VSX","id":"CVE-2026-4983","kev_date_added":null,"published":"2026-06-23"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"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-07-01","vendors":["Eclipse Foundation"]},"summary":"An attacker can inject HTML into the registry to steal tokens and publish malicious extensions, compromising downstream editor users.","url":"https://insights.sbomify.com/CVE-2026-13323/"}