{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-4983 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-4983 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-4983 is a medium-severity cross-site scripting vulnerability in Eclipse Open VSX, published on 23 Jun 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-4983 and fix it if it is affected.\n\nWhat it is: CVE-2026-4983 is a medium-severity cross-site scripting vulnerability in Eclipse Open VSX, published on 23 Jun 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-4983 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-4983/ (Markdown: https://insights.sbomify.com/CVE-2026-4983/index.md)","id":"CVE-2026-4983","markdown":"https://insights.sbomify.com/CVE-2026-4983/index.md","name":"CVE-2026-4983","record":{"aliases":["GHSA-xpqg-5hj3-ggmh"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["account_takeover","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Open VSX Registry","requires_auth":"low_privilege","summary":"Attackers can achieve stored XSS via malicious SVG icons, leading to session hijacking and token theft on local deployments.","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":"Open VSX Registry does not sanitize SVG files uploaded as extension icons prior to storage, and serves them with Content-Type: image/svg+xml without security headers such as Content-Security-Policy or Content-Disposition: attachment. This allows an attacker to publish an extension with a malicious SVG icon and achieve stored cross-site scripting (XSS) when a user navigates directly to the icon URL.\n\nOn deployments using local storage, script execution occurs within the Open VSX application origin, enabling session hijacking, authentication token theft, and unauthorized extension publishing. On deployments backed by external storage (such as open-vsx.org with an S3-backed CDN), execution is confined to the storage origin, reducing impact but still permitting phishing attacks and credential harvesting through attacker-crafted pages.","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-4983","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Botpress - Credential Disclosure via Twilio Webhook Handler","id":"CVE-2026-4984"},"packages":[],"prev":{"headline":"Unauthorized access to chat contents","id":"CVE-2026-4982"},"products":["Eclipse Open VSX"],"published":"2026-06-23","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-13323","kev_date_added":null,"published":"2026-07-01"}],"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-06-23","vendors":["Eclipse Foundation"]},"summary":"Attackers can achieve stored XSS via malicious SVG icons, leading to session hijacking and token theft on local deployments.","url":"https://insights.sbomify.com/CVE-2026-4983/"}