CVE-2026-90882

Reflected arbitrary origins with credentials, allowing cross-origin reads of authenticated user data

Published Sep 22, 2026 CVSS 4.0 · 8.7 High EPSS < 1% KEV · Not listed
Description
The open-vsx.org deployment returned Access-Control-Allow-Origin reflecting the requesting origin together with Access-Control-Allow-Credentials: true on the authenticated /user/ endpoints. A page on any origin could therefore issue credentialed requests to the service in a logged-in user's browser and read the responses.



This exposed /user (login name, avatar, homepage, tokens URL), /user/tokens, /user/namespaces, /user/extensions, /user/search/{name} and /user/namespace/{name}/members, and — because /user/csrf was readable the same way — allowed the CSRF protection on write endpoints to be defeated. Chaining the two, an attacker page could call /user/token/create and exfiltrate a personal access token carrying publish and delete rights over the victim's namespaces.



The headers were emitted by the CDN/edge layer, not by the application: the Open VSX software sets allowCredentials(true) in exactly one place, against a single exact origin derived from ovsx.webui.url, and defines no CORS mapping on /user/ beyond it. No configuration of the software produces origin reflection with credentials.

Analysis

AI-generated

Technical impact

The open‑vsx.org service incorrectly reflected the requesting origin and included the Access‑Control‑Allow‑Credentials header on authenticated /user endpoints. This allowed a page from any origin to perform credentialed requests in a logged‑in user’s browser and read sensitive data such as login name, avatar, homepage, tokens URL, user namespaces, extensions, and search results. The same misconfiguration also let the attacker defeat CSRF protection on write endpoints; by chaining the read and write paths an attacker could trigger /user/token/create and exfiltrate a personal access token with publish and delete rights. The flaw is identified as CWE‑942, a weakness in origin‑based access controls.

Affected Systems

The affected product is the Open VSX platform hosted at open‑vsx.org, maintained by the Eclipse Foundation. The vulnerability resides in the CDN or edge layer that emits the reflected headers and is not controlled by application configuration. Specific version information is not provided in the advisory, so the scope applies to all current deployments of the Open VSX service that rely on the default edge configuration.

Risk and Exploitability

The CVSS score of 8.7 indicates high severity, and the exploit is likely to be simple for any user who can load a malicious page in a victim’s browser. Although the EPSS score is not available, the lack of a KEV listing does not negate the risk; the vulnerability would be trivial to exploit once a user visits a malicious origin. An attacker only needs to host a small page that issues cross‑origin requests; no additional privileges or network access are required. The ease of exploitation and the potential to generate tokens with broad scopes mean that the risk for an impacted organization is significant.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Contact the Open VSX team to fix the CORS configuration by removing allowCredentials(true) for reflected origins and restricting access to /user endpoints to an explicit list of trusted origins.
  • As a temporary measure, block or filter cross‑origin requests to any /user endpoints from untrusted origins at the network or reverse‑proxy level to prevent credentialed requests from other sites.
  • Configure monitoring or logging to alert on the creation or usage of new personal access tokens, and review tokens with publish and delete scopes for unusual activity.

Generated by OpenCVE AI on September 22, 2026 at 10:20 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
First Time appeared Eclipse
Eclipse open-vsx.org
Vendors & Products Eclipse
Eclipse open-vsx.org
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}

Type Values Removed Values Added
Description The open-vsx.org deployment returned Access-Control-Allow-Origin reflecting the requesting origin together with Access-Control-Allow-Credentials: true on the authenticated /user/ endpoints. A page on any origin could therefore issue credentialed requests to the service in a logged-in user's browser and read the responses. This exposed /user (login name, avatar, homepage, tokens URL), /user/tokens, /user/namespaces, /user/extensions, /user/search/{name} and /user/namespace/{name}/members, and — because /user/csrf was readable the same way — allowed the CSRF protection on write endpoints to be defeated. Chaining the two, an attacker page could call /user/token/create and exfiltrate a personal access token carrying publish and delete rights over the victim's namespaces. The headers were emitted by the CDN/edge layer, not by the application: the Open VSX software sets allowCredentials(true) in exactly one place, against a single exact origin derived from ovsx.webui.url, and defines no CORS mapping on /user/ beyond it. No configuration of the software produces origin reflection with credentials.
Title Reflected arbitrary origins with credentials, allowing cross-origin reads of authenticated user data
Weaknesses CWE-942
References
Metrics cvssV4_0

{'score': 8.7, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N'}

Weaknesses
  • CWE-942

    Permissive Cross-domain Security Policy with Untrusted Domains

Sources

Status
PUBLISHED
Assigner
eclipse
Published
Updated
Sep 22, 2026, 1:06 PM
Reserved
Sep 14, 2026, 7:44 AM
Status
Awaiting Analysis
Published
Sep 22, 2026, 10:17 AM
Modified
Sep 22, 2026, 7:09 PM