Withdrawn: this CVE is not a vulnerability
The assigning CNA withdrew CVE-2026-49030 on 13 September 2026, and it carries the Rejected state at CVE.org and NVD. It must not be treated as a live finding. Its pre-withdrawal severity, score and exploitability are withheld below; the record itself is kept because withdrawals are reversible and because the reject reason is the correction worth publishing.
CVE-2026-49030
Pathe Path Traversal Vulnerability
Description
Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: This candidate was withdrawn by its CNA. Further investigation showed that it was not a security issue. Notes: none.
INFO
Published Date :
Sept. 13, 2026, 9:17 p.m.
Last Modified :
Sept. 13, 2026, 10:16 p.m.
Remotely Exploit :
—
Source :
[email protected]
Affected Products
The following products are affected by CVE-2026-49030
vulnerability.
Even if cvefeed.io is aware of the exact versions of the
products
that
are
affected, the information is not represented in the table below.
No affected product recoded yet
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2026-49030 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2026-49030 vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
CVE Rejected by [email protected]
Sep. 13, 2026
Action Type Old Value New Value -
CVE Modified by [email protected]
Sep. 13, 2026
Action Type Old Value New Value Removed Tag MITRE: disputed Changed Description pathe through 2.0.3 unconditionally normalizes backslash characters to forward slashes on all platforms, including POSIX systems where backslash is a valid filename character. This causes join(), resolve(), and normalize() to interpret backslash-separated dot notation sequences as directory traversal, diverging from Node.js path.posix behavior and enabling path traversal attacks that bypass common input validation in server-side applications. NOTE: the Supplier reports that "the behavior is documented, intentional, and identical in spirit to path.win32." Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: This candidate was withdrawn by its CNA. Further investigation showed that it was not a security issue. Notes: none. Added Affected Affected value removed. <a href="https://github.com/CVEProject/cvelistV5/blob/main/cves/2026/49xxx/CVE-2026-49030.json">CVE-2026-49030</a> Removed Reference MITRE: https://github.com/unjs/pathe/issues/240 -
New CVE Received by [email protected]
Sep. 13, 2026
Action Type Old Value New Value Added Tag disputed Added Description pathe through 2.0.3 unconditionally normalizes backslash characters to forward slashes on all platforms, including POSIX systems where backslash is a valid filename character. This causes join(), resolve(), and normalize() to interpret backslash-separated dot notation sequences as directory traversal, diverging from Node.js path.posix behavior and enabling path traversal attacks that bypass common input validation in server-side applications. NOTE: the Supplier reports that "the behavior is documented, intentional, and identical in spirit to path.win32." Added Affected New affected value received. <a href="https://github.com/CVEProject/cvelistV5/blob/main/cves/2026/49xxx/CVE-2026-49030.json">CVE-2026-49030</a> Added Reference https://github.com/unjs/pathe/issues/240