CVE-2026-44522: CWE-20: Improper Input Validation in enchant97 note-mark
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.
AI Analysis
Technical Summary
The Note Mark application (versions >= 0.13.0 and < 0.19.4) suffers from improper input validation (CWE-20) and directory traversal (CWE-22) in its asset upload feature. Authenticated users can specify asset filenames via the X-Name HTTP header without sanitization. These filenames are stored as-is in the database and later used in filepath.Join() calls during export commands, which resolve directory traversal sequences like '../'. This leads to arbitrary file write outside the export directory during the export process. The issue is resolved in version 0.19.4.
Potential Impact
An attacker with authenticated access can craft asset filenames containing directory traversal sequences that cause the export process to write files to arbitrary locations on the filesystem. This can lead to unauthorized file creation or overwriting, potentially compromising system integrity or confidentiality. The vulnerability has a high CVSS 4.0 score of 8.6, indicating significant impact if exploited.
Mitigation Recommendations
This vulnerability is fixed in Note Mark version 0.19.4. Users should upgrade to version 0.19.4 or later to remediate this issue. There is no official vendor advisory provided here, but the fix is confirmed in the version history. Until upgraded, restrict authenticated user privileges and avoid running export commands on untrusted data.
CVE-2026-44522: CWE-20: Improper Input Validation in enchant97 note-mark
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.
CVSS v4.0
Score 8.6high
Affected software
pkg:github/enchant97/note-markRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The Note Mark application (versions >= 0.13.0 and < 0.19.4) suffers from improper input validation (CWE-20) and directory traversal (CWE-22) in its asset upload feature. Authenticated users can specify asset filenames via the X-Name HTTP header without sanitization. These filenames are stored as-is in the database and later used in filepath.Join() calls during export commands, which resolve directory traversal sequences like '../'. This leads to arbitrary file write outside the export directory during the export process. The issue is resolved in version 0.19.4.
Potential Impact
An attacker with authenticated access can craft asset filenames containing directory traversal sequences that cause the export process to write files to arbitrary locations on the filesystem. This can lead to unauthorized file creation or overwriting, potentially compromising system integrity or confidentiality. The vulnerability has a high CVSS 4.0 score of 8.6, indicating significant impact if exploited.
Mitigation Recommendations
This vulnerability is fixed in Note Mark version 0.19.4. Users should upgrade to version 0.19.4 or later to remediate this issue. There is no official vendor advisory provided here, but the fix is confirmed in the version history. Until upgraded, restrict authenticated user privileges and avoid running export commands on untrusted data.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-05-06T19:38:10.566Z
- Cvss Version
- 4.0
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a062b6cec166c07b00def8a
Added to database: 05/14/2026, 20:07:08 UTC
Last enriched: 05/14/2026, 20:21:56 UTC
Last updated: 07/06/2026, 08:51:19 UTC
Views: 83
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.