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.
CVE-2026-44522
This high-severity CVE scores 8.6 under NVD CVSS v3. EPSS exploit probability: 0.5%, top 61% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 8.6
- EG Score
- 8.6(medium)
- EPSS
- 39.0%
- KEV
- Not listed
Published
May 14, 2026
Last Modified
May 15, 2026
Advisory Details (1)
Auto-updated May 14, 2026Arbitrary File Write via Path Traversal in Asset Names Leading to Remote Code Execution · Advisory · enchant97/note-mark · GitHub
https://github.com/enchant97/note-mark/security/advisories/GHSA-g49p-4qxj-88v3Vendor Advisories for CVE-2026-44522(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(1 across 1 ecosystem)
Go(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| github.com/enchant97/note-mark/backend | — | 0.0.0-20260501152243-db3f72bff780 | — |
Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 5× in last 7d / 45× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
Showing the most recent 100 of 101 total refreshes for this CVE.
- 2026-07-11 08:27 UTCEPSS rescore
- 2026-07-09 19:10 UTCEPSS rescore
- 2026-07-08 15:16 UTCEPSS rescore
- 2026-07-06 16:27 UTCEPSS rescore
- 2026-07-06 02:23 UTCEPSS rescore
- 2026-07-05 02:30 UTCEPSS rescore
- 2026-07-04 06:31 UTCEPSS rescore
- 2026-07-01 15:07 UTCEPSS rescore
- 2026-06-30 23:22 UTCEPSS rescore
- 2026-06-29 21:48 UTCEG score recompute
- 2026-06-29 14:06 UTCEPSS rescore
- 2026-06-28 14:07 UTCEPSS rescore
- 2026-06-28 11:30 UTCEG score recompute
- 2026-06-28 04:56 UTCEPSS rescore
- 2026-06-27 22:38 UTCEG score recompute
- 2026-06-27 09:14 UTCEG score recompute
- 2026-06-27 03:08 UTCEPSS rescore
- 2026-06-26 20:21 UTCEG score recompute
- 2026-06-25 19:10 UTCEG score recompute
- 2026-06-25 13:49 UTCEPSS rescore
- 2026-06-25 13:49 UTCEPSS rescore
- 2026-06-24 14:05 UTCEPSS rescore
- 2026-06-23 21:33 UTCEPSS rescore
- 2026-06-22 14:25 UTCEPSS rescore
- 2026-06-22 14:25 UTCEPSS rescore
Show 75 moreShow fewer
- 2026-06-21 14:56 UTCEPSS rescore
- 2026-06-21 14:56 UTCEPSS rescore
- 2026-06-21 01:59 UTCEPSS rescore
- 2026-06-19 19:25 UTCEPSS rescore
- 2026-06-18 17:52 UTCEPSS rescore
- 2026-06-18 17:52 UTCEPSS rescore
- 2026-06-17 17:53 UTCEPSS rescore
- 2026-06-17 13:48 UTCEG score recompute
- 2026-06-16 22:20 UTCEG score recompute
- 2026-06-16 17:52 UTCEPSS rescore
- 2026-06-15 23:57 UTCEG score recompute
- 2026-06-15 17:49 UTCEPSS rescore
- 2026-06-15 01:11 UTCEG score recompute
- 2026-06-14 12:20 UTCEG score recompute
- 2026-06-13 23:29 UTCEG score recompute
- 2026-06-13 23:00 UTCEPSS rescore
- 2026-06-13 02:51 UTCEG score recompute
- 2026-06-12 23:12 UTCEPSS rescore
- 2026-06-12 23:12 UTCEPSS rescore
- 2026-06-12 14:00 UTCEG score recompute
- 2026-06-12 01:08 UTCEG score recompute
- 2026-06-11 14:00 UTCEPSS rescore
- 2026-06-11 12:17 UTCEG score recompute
- 2026-06-10 23:26 UTCEG score recompute
- 2026-06-10 22:18 UTCEPSS rescore
- 2026-06-10 13:22 UTCEPSS rescore
- 2026-06-10 13:22 UTCEPSS rescore
- 2026-06-10 10:34 UTCEG score recompute
- 2026-06-09 21:43 UTCEG score recompute
- 2026-06-09 08:44 UTCEG score recompute
- 2026-06-08 19:52 UTCEG score recompute
- 2026-06-08 14:17 UTCEPSS rescore
- 2026-06-08 14:17 UTCEPSS rescore
- 2026-06-08 05:14 UTCEG score recompute
- 2026-06-07 16:23 UTCEG score recompute
- 2026-06-07 15:25 UTCEPSS rescore
- 2026-06-07 15:25 UTCEPSS rescore
- 2026-06-07 03:32 UTCEG score recompute
- 2026-06-06 14:41 UTCEG score recompute
- 2026-06-06 13:47 UTCEPSS rescore
- 2026-06-06 13:47 UTCEPSS rescore
- 2026-06-06 01:49 UTCEG score recompute
- 2026-06-05 22:47 UTCEPSS rescore
- 2026-06-05 12:58 UTCEG score recompute
- 2026-06-05 06:10 UTCEPSS rescore
- 2026-06-05 06:10 UTCEPSS rescore
- 2026-06-05 00:07 UTCEG score recompute
- 2026-06-04 13:12 UTCEPSS rescore
- 2026-06-04 13:12 UTCEPSS rescore
- 2026-06-04 10:52 UTCEG score recompute
- 2026-06-03 22:01 UTCEG score recompute
- 2026-06-03 09:10 UTCEG score recompute
- 2026-06-02 20:19 UTCEG score recompute
- 2026-06-02 20:13 UTCEPSS rescore
- 2026-06-02 07:28 UTCEG score recompute
- 2026-06-01 18:37 UTCEG score recompute
- 2026-06-01 13:52 UTCEPSS rescore
- 2026-06-01 13:52 UTCEPSS rescore
- 2026-06-01 05:46 UTCEG score recompute
- 2026-05-31 22:30 UTCEPSS rescore
- 2026-05-31 22:30 UTCEPSS rescore
- 2026-05-31 00:16 UTCEPSS rescore
- 2026-05-31 00:16 UTCEPSS rescore
- 2026-05-29 13:44 UTCEPSS rescore
- 2026-05-29 13:44 UTCEPSS rescore
- 2026-05-28 13:44 UTCEPSS rescore
- 2026-05-28 13:44 UTCEPSS rescore
- 2026-05-27 13:40 UTCEPSS rescore
- 2026-05-27 13:40 UTCEPSS rescore
- 2026-05-26 13:44 UTCEPSS rescore
- 2026-05-26 07:18 UTCEPSS rescore
- 2026-05-23 00:07 UTCEG score recompute
- 2026-05-21 22:43 UTCEPSS rescore
- 2026-05-20 22:38 UTCEPSS rescore
- 2026-05-20 12:13 UTCEG score recompute
Related CVEs(same CWE)
Same CWE
10 shownCWE-20 · CWE-22
- CVE-2002-2444EG 9.8CRITICAL
- CVE-2002-1359NVD 0.0EG 9.0EPSS 100%NONE
- CVE-2001-0925NVD 0.0EG 9.0EPSS 99%NONE
- CVE-2000-0380NVD 0.0EG 9.0EPSS 98%NONE
- CVE-2000-0258EG 7.5EPSS 97%HIGH
- CVE-2002-2443EG 0.0EPSS 93%NONE
- CVE-2002-2433EG 0.0NONE
- CVE-2001-1586EG 0.0EPSS 94%NONE
- CVE-2002-2429EG 0.0NONE
- CVE-2002-2428EG 0.0NONE
Frequently asked(5)
What is CVE-2026-44522?
When was CVE-2026-44522 disclosed?
Is CVE-2026-44522 actively exploited?
What is the CVSS score of CVE-2026-44522?
How do I remediate CVE-2026-44522?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-44522
Is Your Infrastructure Affected by CVE-2026-44522?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.