Summary
A maliciously crafted URL using the proxy subpath can result in the attacker gaining access to the session token.
Details
Failure to properly validate the port for a proxy request can result in proxying to an arbitrary domain. The malicious URL https://<code-server>/proxy/[email protected]/path would be proxied to [email protected]/path where the attacker could exfiltrate a user's session token.
Impact
Any user who runs code-server with the built-in proxy enabled and clicks on maliciously crafted links that go to their code-server instances with reference to /proxy.
Normally this is used to proxy local ports, however the URL can reference the attacker's domain instead, and the connection is then proxied to that domain, which will include sending cookies.
With access to the session cookie, the attacker can then log into code-server and have full access to the machine hosting code-server as the user running code-server.
CVE-2025-47269 has a CVSS score of 8.3 (High). The vector is network-reachable, no privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (4.99.4); upgrading removes the vulnerable code path.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Remediation advice
Patched versions are from v4.99.4 onward.
Frequently Asked Questions
- What is CVE-2025-47269? CVE-2025-47269 is a high-severity security vulnerability in code-server (npm), affecting versions < 4.99.4. It is fixed in 4.99.4.
- How severe is CVE-2025-47269? CVE-2025-47269 has a CVSS score of 8.3 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
- Which versions of code-server are affected by CVE-2025-47269? code-server (npm) versions < 4.99.4 is affected.
- Is there a fix for CVE-2025-47269? Yes. CVE-2025-47269 is fixed in 4.99.4. Upgrade to this version or later.
- Is CVE-2025-47269 exploitable, and should I be worried? Whether CVE-2025-47269 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2025-47269 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2025-47269? Upgrade
code-serverto 4.99.4 or later.