Cyber Resilience

CVE-2025-6705

High

Published: 27 June 2025

Published
27 June 2025
Modified
31 July 2025
KEV Added
Patch
CVSS Score v4 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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
EPSS Score 0.0021 43.7th percentile
Risk Priority 15 60% EPSS · 20% KEV · 20% CVSS

Summary

CVE-2025-6705 is a high-severity Improper Isolation or Compartmentalization (CWE-653) vulnerability in Eclipse Open Vsx. Its CVSS base score is 7.6 (High).

Operationally, ranked at the 43.7th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

EU & UK References

Vulnerability details

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…

more

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.

CWE(s)

Related Threats

No named actor attribution yet. ATT&CK technique mapping in progress for this CVE.

Affected Assets

eclipse
open vsx
all versions

Mitigating Controls

Likely Mitigating Controls AI

Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.

addresses: CWE-653

Defines isolation boundaries by specifying which external systems may access or process organization data.

addresses: CWE-653

Maintains isolation and compartmentalization by restricting flows between security domains or levels.

addresses: CWE-653

Reviewing the continued need for connections supports isolation and compartmentalization.

addresses: CWE-653

Locating systems away from hazards improves isolation and compartmentalization from external physical or environmental threats.

addresses: CWE-653

The CONOPS must articulate isolation and compartmentalization expectations for security and privacy, making architectural failures in separation of duties or domains harder to overlook.

addresses: CWE-653

Security architectures commonly incorporate isolation and compartmentalization strategies to limit the impact of compromises.

addresses: CWE-653

Organization-wide privacy program leadership ensures proper isolation and compartmentalization of personal data.

addresses: CWE-653

Oversight ensures data-matching activities maintain required isolation between distinct data sets and authorized user communities.

References