CVE-2025-47269
HIGHEPSS 98th pctlDescription
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.
How to fix
No published remediation has been found for this vulnerability's affected products yet.
Mitigation guidance may be in the linked vendor advisories in the References section below.
TridentStack Control tracks known vulnerabilities across your Windows, macOS, and Linux fleet and shows the fix as soon as one is published. See how it works
CVSS v3 Vector
Exploitability
Impact
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:L
Exploit Intelligence
Very high risk: more likely to be exploited than 98% of all known CVEs.
References
Related Vulnerabilities
Other CWE-441 vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2019-3924 | High | 7.5 | 16% | - | Fix |
| CVE-2020-5412 | Medium | 6.5 | 10% | - | Fix |
| CVE-2019-3996 | Medium | 6.5 | 5.9% | - | - |
| CVE-2021-20042 | Critical | 9.8 | 2.7% | - | - |
| CVE-2019-1841 | Medium | 6.5 | 2.6% | - | Fix |
| CVE-2020-8561 | Medium | 4.1 | 2.1% | - | Fix |
Common questions
How do I fix CVE-2025-47269?
No published fix for CVE-2025-47269 has been found yet. Check the linked vendor advisories for guidance as it becomes available.
Is CVE-2025-47269 being actively exploited?
Not that we know of. CVE-2025-47269 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 37.8% is the estimated probability that it will be exploited in the next 30 days. That is higher than 98% of all scored CVEs.
How severe is CVE-2025-47269?
CVE-2025-47269 has a CVSS v3 base score of 8.3, rated high. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
Embed a live status badge for CVE-2025-47269
Markdown
[](https://tridentstack.com/cve/CVE-2025-47269)HTML
<a href="https://tridentstack.com/cve/CVE-2025-47269"><img src="https://tridentstack.com/cve/badge/CVE-2025-47269.svg" alt="CVE-2025-47269"></a>Find and fix vulnerabilities across your fleet
TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2025-05-12.