cve.bz

CVE-2025-12999 eclipse foundation eclipse open vsx

9.1 criticalEPSS 0.3%

Critical (9.1) in eclipse foundation eclipse open vsx. EPSS 0.3% estimated probability of exploitation activity in the next 30 days.

On this page
UrlUtil.getBaseUrl builds the absolute URLs in a response — download links, icons, asset and API URLs — from the X-Forwarded-Host, X-Forwarded-Proto and X-Forwarded-Prefix request headers, with no check on whether the sender was a trusted proxy, falling back to the client-supplied Host header. Those responses are cached under keys that do not include the host (extension.json since 0.6.0, namespace.details.json since 0.9.0, sitemap since 0.14.5, latest.extension.version.vscode since 0.34.2). A single request carrying a forged header therefore places attacker-chosen URLs into an entry served to every other client for the lifetime of that entry — one hour by default, and cluster-wide where ovsx.redis.enabled is set. The VSIX download URL, its signature URL and the public key URL are all derived from the same base URL, so extension signing does not limit the impact: an attacker who poisons an entry supplies the package, the signature over it, and the key used to verify it. Exploitability depends on deployment topology. A server reachable directly by clients, or fronted by a proxy that relays the client's X-Forwarded-Host rather than overwriting it, is exploitable by an unauthenticated remote attacker. A proxy that overwrites the header is not. An unauthenticated attacker can poison Open VSX's per-extension metadata cache with attacker-controlled download, signature, and public-key URLs by supplying a crafted X-Forwarded-Host header, causing downstream VS Code-compatible editors to fetch and install a malicious VSIX. Workarounds (unpatched versions) 1. Configure the reverse proxy to set rather than relay X-Forwarded-Host, X-Forwarded-Proto and X-Forwarded-Prefix — note that nginx's $host is the client's Host header and is not a safe value. 2. Ensure the server is not reachable except through that proxy. 3. Flush the caches afterwards; poisoned entries survive the configuration change.

Severity

CVSS 4.0

9.1 critical
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:H/VA:L/SC:H/SI:H/SA:H
EPSS
0.3% (unchanged from 0.3% a week ago; 0.3% 30 days ago) estimated probability of exploitation activity in the next 30 days; 26th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: PoC · Automatable: no · Technical impact: partial, assessed 2026-09-21. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-345 Insufficient Verification of Data Authenticity
OWASP Top 10
A08:2025 Software or Data Integrity Failures
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Ask an AI about this CVE

Show the promptExplain CVE-2025-12999 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2025-12999?via=ask-ai-copy and https://cve.bz/cve/CVE-2025-12999?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2025-12999 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

  • eclipse foundation:eclipse open vsx

Versions

From the CNA's record in the CVE List.

ProductAffected
Eclipse Foundation Eclipse Open VSXfrom 0.6.0 through 1.1.2

Red Hat

Red Hat rates this Critical.

Red Hat's statement

This flaw is rated Critical because it lets an unauthenticated remote attacker run code inside the workspace of a Dev Spaces user, and the preconditions hold in a default installation. Both preconditions were confirmed on a running default Dev Spaces 3.x install by Dev Spaces engineering: the plugin registry search endpoint answers 200 without login, and a client-supplied X-Forwarded-Host reaches the Open VSX server unmodified because the ingress proxy appends the real host as a second header value while the server reads the first one.

The Open VSX server embedded in the plugin registry builds extension download, signature, and public key URLs from that unvalidated header, and caches those responses per extension. One crafted request fixes the URLs every other client gets for the next hour. Since the attacker controls the package, signature, and key together, signature verification does not help.

The only bounding condition is the cache entry being empty when the poisoned request arrives; it recurs hourly. Dev Spaces 3.28, 3.29 and 3.30 ship affected versions (0.34.5, 1.0.1, 1.1.1; fixed in 1.2.0). Fixes are released only for the current minor version, so 3.30 receives the fix in a z-stream update while 3.28 and 3.29 will not receive one. Customers on 3.28 or 3.29 should upgrade to 3.30 to get the fix.

Red Hat's mitigation

On installations that cannot upgrade to a fixed version yet, reconfigure the proxy in front of the Open VSX server to set X-Forwarded-Host, X-Forwarded-Proto and X-Forwarded-Prefix to known values instead of relaying client input, and make sure the server is not reachable except through that proxy. Existing poisoned cache entries survive the configuration change, so flush the Open VSX caches afterwards.

ProductPackageStateAdvisory
Red Hat OpenShift Dev Spacesdevspaces/openvsx-rhel9Affected
Red Hat OpenShift Dev Spacesdevspaces/pluginregistry-rhel9Affected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2025-12999.

Attack patterns (CAPEC)

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-345 (12).

References

Check your stackJSON