Unauthorized extension publishing via unsandboxed build scripts
Published Jun 27, 2025 · Updated Jul 2, 2025
Improper isolation in Eclipse Open VSX Registry before June 24, 2025 allows remote authenticated users to publish extension versions. The auto-publishing workflow ran extension-controlled build scripts without sandboxing, allowing those scripts to read its privileged registry token. Exploitation requires control of an accepted auto-published extension or later malicious code in a manually approved addition; the token creates new versions but cannot overwrite or delete existing releases.
Summary
What happened
Improper isolation in Eclipse Open VSX Registry before June 24, 2025 allows remote authenticated users to publish extension versions. The auto-publishing workflow ran extension-controlled build scripts without sandboxing, allowing those scripts to read its privileged registry token. Exploitation requires control of an accepted auto-published extension or later malicious code in a manually approved addition; the token creates new versions but cannot overwrite or delete existing releases.
The record
- CVE
- CVE-2025-6705
- Published
- Jun 27, 2025
- Updated
- Jul 2, 2025
- Vendor
- The Eclipse Foundation
- Product
- Open VSX Registry
- Classifications
- CWE-653, CWE-913, T1195.002
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 27, 2025CVE publishedPublication date reported by the CVE source.
- Jul 2, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=date < 20250624
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo