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

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

8.6 · 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 · score source

EPSS

• CVE-2026-44522: 0.56% estimated exploitation activity in the next 30 days; percentile 46.97 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Description 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 noteassets 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…

Published by the source

7 May 2026, 21:06 UTC

Last modified by the source

15 May 2026, 23:45 UTC

Source last checked

26 Oct 2026, 15:22 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-g49p-4qxj-88v3

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-44522

Advisory: Note Mark: Arbitrary File Write via Path Traversal in Asset Names Leads to Remote Code Execution
IDs: CVE-2026-44522, GHSA-g49p-4qxj-88v3
Record: https://patchnext.com/advisories/cve-2026-44522 (revision 1, source checked 26 Oct 2026, 15:22 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.6)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/enchant97/note-mark/backend 0.0.0-20260501152243-db3f72bff780. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/enchant97/note-mark/backend: affected < 0.0.0-20260501152243-db3f72bff780; fixed in 0.0.0-20260501152243-db3f72bff780

## Suggested inspection (read-only)
- Go github.com/enchant97/note-mark/backend: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/enchant97/note-mark/backend.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-g49p-4qxj-88v3 (GitHub-reviewed advisory GHSA-g49p-4qxj-88v3 lists affected ranges: Go github.com/enchant97/note-mark/backend >=0 <0.0.0-20260501152243-db3f72bff780)

Commands are suggestions: review each one before running it.