Advisory record · GHSA-g49p-4qxj-88v3

Note Mark: Arbitrary File Write via Path Traversal in Asset Names Leads to Remote Code Execution

CVSS 8.6 HighEPSS 0.0056 · 47th percentile

Published by the GitHub Advisory Database at 7 May 2026, 21:06 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
github.com/enchant97/note-mark/backendGo<0.0.0-20260501152243-db3f72bff7800.0.0-20260501152243-db3f72bff780
Identifiers
GHSA-g49p-4qxj-88v3 · CVE-2026-44522 · GO-2026-5389
Weakness (CWE)
CWE-20 · CWE-22
Published
7 May 2026
Updated
25 Jun 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Note Mark (Go module github.com/enchant97/note-mark/backend) versions up to and including 0.0.0-20260501152243-db3f72bff780 are affected, and the fix is listed as 0.0.0-20260501152243-db3f72bff780. An authenticated user can upload an asset with a path traversal name, and when an administrator runs the migrate export commands, the export can write files outside the export directory, which the source says may lead to code execution as root. Upgrade to the fixed version; the source suggests validating asset names so that they contain no path separators or traversal sequences.

Written 7 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
8.6 High 4.0 CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0056, the 47th percentile, on 16 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 15:07 UTC First seen by agentprime
  2. 31 Oct 2026, 15:07 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.