{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-6705 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-6705 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-6705 is a high-severity vulnerability in Eclipse Open VSX Registry, published on 27 Jun 2025. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-6705 and fix it if it is affected.\n\nWhat it is: CVE-2025-6705 is a high-severity vulnerability in Eclipse Open VSX Registry, published on 27 Jun 2025. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-6705 in the wild and no public exploit code.\n\nAffected product: Eclipse Open VSX Registry. 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-2025-6705/ (Markdown: https://insights.sbomify.com/CVE-2025-6705/index.md)","id":"CVE-2025-6705","markdown":"https://insights.sbomify.com/CVE-2025-6705/index.md","name":"CVE-2025-6705","record":{"aliases":["GHSA-wrfh-r93c-gw3f"],"analysis":{"component_type":"cloud_service","fix_type":"patch","impacts":["privilege_escalation","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Extension Registry","requires_auth":"low_privilege","summary":"Attackers could exploit build script isolation flaws to obtain privileged tokens and publish unauthorized extensions under any namespace.","user_interaction":"not_required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"eclipse","cpe":[{"product":"open_vsx","vendor":"eclipse"}],"cvss":{"score":7.6,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-913","name":"Improper Control of Dynamically-Managed Code Resources"},{"id":"CWE-653","name":"Improper Isolation or Compartmentalization"}],"description":"A vulnerability in the Eclipse Open VSX Registry’s automated publishing system could have allowed unauthorized uploads of extensions. Specifically, the system’s build scripts were executed without proper isolation, potentially exposing a privileged token. This token enabled the publishing of new extension versions under any namespace, including those not controlled by an attacker. However, it did not permit deletion of existing extensions, overwriting of published versions, or access to administrative features of the registry.\n\nThe issue was reported on May 4, 2025, fully resolved by June 24, and followed by a comprehensive audit. No evidence of compromise was found, though 81 extensions were proactively deactivated as a precaution. The standard publishing process remained unaffected. Recommendations have been issued to mitigate similar risks in the future.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Privilege escalation in Eclipse Open VSX Registry","id":"CVE-2025-6705","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"privilege_escalation","year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"Running certain aggregation operations with the SBE engine may lead to unexpected behavior on MongoDB Server","id":"CVE-2025-6706"},"packages":[],"prev":{"headline":"Command injection in Sophos Firewall","id":"CVE-2025-6704"},"products":["Eclipse Open VSX Registry"],"published":"2025-06-27","related":[{"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"},{"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":"2025-07-02","vendors":["Eclipse Foundation"]},"summary":"Attackers could exploit build script isolation flaws to obtain privileged tokens and publish unauthorized extensions under any namespace.","url":"https://insights.sbomify.com/CVE-2025-6705/"}