We use these services and cookies to improve your user experience. You may opt out if you wish, however, this may limit some features on this site.
Please see our statement on Data Privacy.
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.
Reserved 2025-06-26 | Published 2025-06-27 | Updated 2025-07-02 | Assigner eclipseCWE-913 Improper Control of Dynamically-Managed Code Resources
CWE-653 Improper Isolation or Compartmentalization
Oren Yomtov (Koi Security)
open-vsx.org
github.com/EclipseFdn/publish-extensions/pull/881
Support options
