ZDF
Sign inSign up

Vulnerabilities

Vulnerability · CVE-2025-6705

A vulnerability in the Eclipse Open VSX Registry’s automated publishing system could have allowed unauthorized uploads of extensions.

Published Jun 27, 2025 · catalog updated Jul 2, 2025 · Eclipse Foundation Eclipse Open VSX Registry

Check this week

CVE-2025-6705 is not in CISA KEV. FIRST estimates a 26.00% chance of exploitation in the next 30 days. Check whether you run Eclipse Foundation Eclipse Open VSX Registry.

Gaps on this record

  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
Severity
High7.6
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
26.00%
Remediation
Version ranges on file
Affected products
vendor Eclipse Foundation Eclipse Open VSX Registry date < 20250624

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, a

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • vendor Eclipse Foundation Eclipse Open VSX Registry date < 20250624date < 20250624

How to fix CVE-2025-6705

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

CVE-2025-6705 is not in CISA KEV. FIRST estimates a 26.00% chance of exploitation in the next 30 days. Check whether you run Eclipse Foundation Eclipse Open VSX Registry.

Which versions are affected?

Compare what you have installed with Eclipse Foundation Eclipse Open VSX Registry date < 20250624 date < 20250624. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

No weakness class is stored. EPSS 26.00%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Code

The project this record applies to. Exploit listings stay in References.

Timeline

Detection, updates, and resolution for this record.

  1. Jun 27, 2025 · EUVD

    Detected

    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

  2. Jul 2, 2025 · EUVD

    Updated

    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

Sources

  • CVE.orgVulnerability recordCVE-2025-6705

    Official CVE identifier

    cve.org
  • EUVDVulnerability recordEUVD-2025-19382

    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 p

    euvd.enisa.europa.eu

References

Freshness

Last verified in this catalog Jul 2, 2025. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.