CVSS 4.0
9.1 criticalCVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:H/VA:L/SC:H/SI:H/SA:HCritical (9.1) in eclipse foundation eclipse open vsx. EPSS 0.3% estimated probability of exploitation activity in the next 30 days.
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:H/VA:L/SC:H/SI:H/SA:HExplain 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.
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| Eclipse Foundation Eclipse Open VSX | from 0.6.0 through 1.1.2 |
Red Hat rates this Critical.
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.
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.
| Product | Package | State | Advisory |
|---|---|---|---|
| Red Hat OpenShift Dev Spaces | devspaces/openvsx-rhel9 | Affected | |
| Red Hat OpenShift Dev Spaces | devspaces/pluginregistry-rhel9 | Affected |
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.
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).