CVE-2026-44522 Note Mark: Arbitrary File Write via Path Traversal in Asset Names Leading to Remote Code Execution
Authenticated attackers can write arbitrary files via path traversal in asset names, leading to remote code execution during data export.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- A user has to click or open something
- Fix
- Available
What is CVE-2026-44522?
CVE-2026-44522 is a high-severity path traversal vulnerability in enchant97 note-mark, published on 14 May 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Official description
Note Mark is an open-source note-taking application. From 0.13.0 to before 0.19.4, the Note Mark application allows authenticated users to upload assets to notes via POST /api/notes/{noteID}/assets, where the asset filename is provided through the X-Name HTTP request header. This value is stored directly in the database without any sanitization or validation - no path separator filtering, no directory traversal sequence rejection, and no use of filepath.Base() to strip directory components. The unsanitized name is persisted as-is in the note_assets table (Name column, varchar(80)). When an administrator subsequently runs the data export CLI commands (note-mark migrate export-v1 or note-mark migrate export), the stored asset name is passed directly into filepath.Join() and path.Join() calls as part of the output file path argument to os.Create(). Since Go's filepath.Join() resolves ../ sequences during path normalization, an attacker-controlled asset name containing directory traversal sequences causes the export process to write files to arbitrary locations on the filesystem, completely outside the intended export directory. This vulnerability is fixed in 0.19.4.
Which versions are affected by CVE-2026-44522?
3 open source packages ship an affected version, including github.com/enchant97/note-mark/backend.
| Package | Affected | Fixed in |
|---|---|---|
github.com/enchant97/note-mark/backend Go | All versions | 0.0.0-20260501152243-db3f72bff780 |
github.com/enchant97/note-mark/backend Go | All versions | 0.0.0-20260501152243-db3f72bff780 |
github.com/enchant97/note-mark/backend Go | All versions | 0.0.0-20260501152243-db3f72bff780 |
How do I fix CVE-2026-44522?
Upgrade github.com/enchant97/note-mark/backend to 0.0.0-20260501152243-db3f72bff780 or later.
Upgrade, and resolve every user-supplied path against an allowed base folder before opening it. More about Path traversal.
Is CVE-2026-44522 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-44522 exists.
Sources
Also known as GHSA-g49p-4qxj-88v3, GO-2026-5389.