<?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://db.gcve.eu</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>Thu, 01 Oct 2026 10:25:48 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-53632 — NTLMv2 hash disclosure via UNC path handling on Windows</title>
      <link>https://db.gcve.eu/vuln/cve-2026-53632</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; vitejs launch-editor, vitejs vite, vitejs vite-plus&lt;/p&gt;
&lt;p&gt;launch-editor allows users to open files with line numbers in editor from Node.js. Prior to 2.14.1, the launch-editor NPM package accesses arbitrary paths including Windows UNC paths. When a UNC path is opened, Windows automatically attempts NTLM authentication to the remote host, causing the user’s NTLMv2 password hash to be leaked to an attacker-controlled SMB server. This can result in credential compromise through offline hash cracking. This vulnerability is fixed in 2.14.1.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; vitejs launch-editor, vitejs vite, vitejs vite-plus&lt;/p&gt;
&lt;p&gt;launch-editor allows users to open files with line numbers in editor from Node.js. Prior to 2.14.1, the launch-editor NPM package accesses arbitrary paths including Windows UNC paths. When a UNC path is opened, Windows automatically attempts NTLM authentication to the remote host, causing the user’s NTLMv2 password hash to be leaked to an attacker-controlled SMB server. This can result in credential compromise through offline hash cracking. This vulnerability is fixed in 2.14.1.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2026-53632</guid>
    </item>
    <item>
      <title>GHSA-v6wh-96g9-6wx3 — launch-editor: NTLMv2 hash disclosure via UNC path handling on Windows</title>
      <link>https://db.gcve.eu/vuln/ghsa-v6wh-96g9-6wx3</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: launch-editor, npm: vite, npm: vite-plus&lt;/p&gt;
&lt;p&gt;### Summary
The `launch-editor` NPM package accesses arbitrary paths including Windows UNC paths. When a UNC path is opened, Windows automatically attempts NTLM authentication to the remote host, causing the user’s NTLMv2 password hash to be leaked to an attacker-controlled SMB server. This can result in credential compromise through offline hash cracking.&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;If the following conditions are met, an attacker can get the NTLMv2 password hash on the computer that is using the `launch-editor`:&lt;/p&gt;
&lt;p&gt;- using Windows
- NTLM is not disabled ([it is recommended to disable](https://techcommunity.microsoft.com/blog/windows-itpro-blog/advancing-windows-security-disabling-ntlm-by-default/4489526), while it&amp;#39;s still enabled by default)
- the user accesses the attackers website that sends request to a middleware using `launch-editor`
- the server that has the middleware using `launch-editor` is running
- the attacker knows the URL for that server and the middleware&lt;/p&gt;
&lt;p&gt;This would be a problem if the user password is too simple that it can be identified through offline hash cracking, potentially leading to further compromise of developer accounts or internal systems.&lt;/p&gt;
&lt;p&gt;### Details
`launch-editor` accepts file paths without validating or restricting Windows UNC paths such as:&lt;/p&gt;
&lt;p&gt;```
\\attacker-host\share
```&lt;/p&gt;
&lt;p&gt;On Windows systems, accessing a UNC path triggers an automatic NTLM authentication attempt to the remote SMB server. No user interaction or warning is required for this authentication at…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: launch-editor, npm: vite, npm: vite-plus&lt;/p&gt;
&lt;p&gt;### Summary
The `launch-editor` NPM package accesses arbitrary paths including Windows UNC paths. When a UNC path is opened, Windows automatically attempts NTLM authentication to the remote host, causing the user’s NTLMv2 password hash to be leaked to an attacker-controlled SMB server. This can result in credential compromise through offline hash cracking.&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;If the following conditions are met, an attacker can get the NTLMv2 password hash on the computer that is using the `launch-editor`:&lt;/p&gt;
&lt;p&gt;- using Windows
- NTLM is not disabled ([it is recommended to disable](https://techcommunity.microsoft.com/blog/windows-itpro-blog/advancing-windows-security-disabling-ntlm-by-default/4489526), while it&amp;#39;s still enabled by default)
- the user accesses the attackers website that sends request to a middleware using `launch-editor`
- the server that has the middleware using `launch-editor` is running
- the attacker knows the URL for that server and the middleware&lt;/p&gt;
&lt;p&gt;This would be a problem if the user password is too simple that it can be identified through offline hash cracking, potentially leading to further compromise of developer accounts or internal systems.&lt;/p&gt;
&lt;p&gt;### Details
`launch-editor` accepts file paths without validating or restricting Windows UNC paths such as:&lt;/p&gt;
&lt;p&gt;```
\\attacker-host\share
```&lt;/p&gt;
&lt;p&gt;On Windows systems, accessing a UNC path triggers an automatic NTLM authentication attempt to the remote SMB server. No user interaction or warning is required for this authentication at…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-v6wh-96g9-6wx3</guid>
    </item>
  </channel>
</rss>
