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.
CVSS

No CVSS.

Configurations

No configuration.

History

02 Jul 2025, 07:15

Type Values Removed Values Added
Summary (en) On open-vsx.org https://open-vsx.org/  it was possible to run an arbitrary build scripts for auto-published extensions because of missing sandboxing of CI job runs. An attacker who had access to an existing extension could take over the service account of the marketplace. The issue has been fixed on June 24th, 2025 and the vulnerable code present in the publish-extension code repository. (en) 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.

30 Jun 2025, 18:38

Type Values Removed Values Added
Summary
  • (es) En open-vsx.org (https://open-vsx.org/), era posible ejecutar scripts de compilación arbitrarios para extensiones publicadas automáticamente debido a la falta de la sandbox para las ejecuciones de trabajos de integración continua. Un atacante con acceso a una extensión existente podría tomar el control de la cuenta de servicio del marketplace. El problema se solucionó el 24 de junio de 2025 y el código vulnerable se encuentra en el repositorio de código de la extensión publicada.

27 Jun 2025, 17:15

Type Values Removed Values Added
Summary (en) On open-vsx.org http://open-vsx.org/  it was possible to run an arbitrary build scripts for auto-published extensions because of missing sandboxing of CI job runs. An attacker who had access to an existing extension could take over the service account of the marketplace. The issue has been fixed on June 24th, 2025 and the vulnerable code present in the publish-extension code repository. (en) On open-vsx.org https://open-vsx.org/  it was possible to run an arbitrary build scripts for auto-published extensions because of missing sandboxing of CI job runs. An attacker who had access to an existing extension could take over the service account of the marketplace. The issue has been fixed on June 24th, 2025 and the vulnerable code present in the publish-extension code repository.

27 Jun 2025, 15:15

Type Values Removed Values Added
New CVE

Information

Published : 2025-06-27 15:15

Updated : 2025-07-02 07:15


NVD link : CVE-2025-6705

Mitre link : CVE-2025-6705

CVE.ORG link : CVE-2025-6705


JSON object : View

Products Affected

No product.

CWE
CWE-653

Insufficient Compartmentalization

CWE-913

Improper Control of Dynamically-Managed Code Resources