CVE-2025-6705

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. The 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.
Configurations

Configuration 1 (hide)

cpe:2.3:a:eclipse:open_vsx:-:*:*:*:*:*:*:*

History

31 Jul 2025, 16:12

Type Values Removed Values Added
CVSS v2 : unknown
v3 : unknown
v2 : unknown
v3 : 5.3
CPE cpe:2.3:a:eclipse:open_vsx:-:*:*:*:*:*:*:*
First Time Eclipse
Eclipse open Vsx
References () https://github.com/EclipseFdn/publish-extensions/pull/881 - () https://github.com/EclipseFdn/publish-extensions/pull/881 - Issue Tracking
References () https://open-vsx.org - () https://open-vsx.org - Product

02 Jul 2025, 07:15

Type Values Removed Values Added
New CVE

Information

Published : 2025-06-27 15:15

Updated : 2025-07-31 16:12


NVD link : CVE-2025-6705

Mitre link : CVE-2025-6705

CVE.ORG link : CVE-2025-6705


JSON object : View

Products Affected

eclipse

  • open_vsx
CWE
CWE-653

Improper Isolation or Compartmentalization

CWE-913

Improper Control of Dynamically-Managed Code Resources