<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://db.gcve.eu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-01T10:25:50.848885+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@gcve.eu</email>
  </author>
  <link href="https://db.gcve.eu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://db.gcve.eu/vuln/cve-2026-53632</id>
    <title>CVE-2026-53632 — NTLMv2 hash disclosure via UNC path handling on Windows</title>
    <updated>2026-10-01T10:25:50.850334+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> vitejs launch-editor, vitejs vite, vitejs vite-plus</p>
<p>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.</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/cve-2026-53632"/>
  </entry>
  <entry>
    <id>https://db.gcve.eu/vuln/ghsa-v6wh-96g9-6wx3</id>
    <title>GHSA-v6wh-96g9-6wx3 — launch-editor: NTLMv2 hash disclosure via UNC path handling on Windows</title>
    <updated>2026-10-01T10:25:50.850421+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> npm: launch-editor, npm: vite, npm: vite-plus</p>
<p>### 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.</p>
<p>### Impact</p>
<p>If the following conditions are met, an attacker can get the NTLMv2 password hash on the computer that is using the `launch-editor`:</p>
<p>- 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'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</p>
<p>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.</p>
<p>### Details
`launch-editor` accepts file paths without validating or restricting Windows UNC paths such as:</p>
<p>```
\\attacker-host\share
```</p>
<p>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…</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/ghsa-v6wh-96g9-6wx3"/>
  </entry>
</feed>
