# CVE-2025-6705: Privilege escalation in Eclipse Open VSX Registry

> Attackers could exploit build script isolation flaws to obtain privileged tokens and publish unauthorized extensions under any namespace.

- **Severity:** High 7.6 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Jun 2025
- **Updated:** 2 Jul 2025
- **Also known as:** GHSA-wrfh-r93c-gw3f

## What is CVE-2025-6705?

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.

### Official 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.

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.

Weakness: CWE-913 (Improper Control of Dynamically-Managed Code Resources), CWE-653 (Improper Isolation or Compartmentalization)

## Which versions are affected by CVE-2025-6705?

It affects 1 product.


Products: Eclipse Open Vsx.

## How do I fix CVE-2025-6705?

No fix has been published for CVE-2025-6705 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-6705 being exploited?

There is no known exploitation of CVE-2025-6705 in the wild and no public exploit code.

## Other vulnerabilities in Eclipse Open VSX Registry

- [CVE-2025-1007](https://insights.sbomify.com/CVE-2025-1007/): Improper Authorization in /user/namespace/{namespace}/details (medium 6.9)
- [CVE-2026-13323](https://insights.sbomify.com/CVE-2026-13323/): Cross-site scripting in Eclipse Open VSX (medium 4.1)
- [CVE-2026-4983](https://insights.sbomify.com/CVE-2026-4983/): Cross-site scripting in Eclipse Open VSX (medium 4.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-6705 and fix it if it is affected.

What 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.
Exploitation: There is no known exploitation of CVE-2025-6705 in the wild and no public exploit code.

Affected product: Eclipse Open VSX Registry. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-6705/ (Markdown: https://insights.sbomify.com/CVE-2025-6705/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-6705
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-6705
- OSV: https://osv.dev/vulnerability/CVE-2025-6705

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-6705/
Summaries are generated and may contain mistakes; the official description above is the record.