Skip to content

← Actionable
High, CVSS 8.6

Note Mark: Path traversal via unsanitized book/note slug in migrate export (sibling of GHSA-g49p)

CVE-2026-50553GHSA-rqrh-8wpv-x7hh

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (github.com/enchant97/note-mark/backend 0.0.0-20260601210719-67b7de04308a), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Affected packages

Sources

Severity and exploitation
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-50553: 0.46% estimated exploitation activity in the next 30 days; percentile 39.80 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Summary Note Mark validates book and note slug values with the OpenAPI/huma tag pattern:"[a-z0-9-]+". huma compiles this with regexp.MustCompile(s.Pattern) and tests it with patternRe.MatchString(str), an UNANCHORED match. Because the pattern is not anchored (^...$), any string that merely CONTAINS one [a-z0-9-] substring passes validation. A slug such as ../../../../../../tmp/escape is accepted and stored verbatim. The data-export CLI commands (note-mark migrate export and note-mark migrate export-v1) join these unsanitized slugs straight into the output path with path.Join / filepath.Join, then os.MkdirAll the directory and os.Create the note file. path.Join resolves the ../ segments, so the note content file is written OUTSIDE the configured export directory. The export process commonly runs as root (default in Docker / bare-metal admin usage), so this is a root-privilege arbitrary directory create + file write. This is the unguarded sibling of GHSA-g49p-4qxj-88v3 (CVE class…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 1 · created ·

    Published from ghsa record GHSA-rqrh-8wpv-x7hh

Agent brief

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

# Patch Next advisory brief: CVE-2026-50553

Advisory: Note Mark: Path traversal via unsanitized book/note slug in migrate export (sibling of GHSA-g49p)
IDs: CVE-2026-50553, GHSA-rqrh-8wpv-x7hh
Record: https://patchnext.com/advisories/cve-2026-50553 (revision 1, source checked 26 Oct 2026, 15:24 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-20260601210719-67b7de04308a. A vendor fix does not mean a deployment is fixed.

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

## 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-rqrh-8wpv-x7hh (GitHub-reviewed advisory GHSA-rqrh-8wpv-x7hh lists affected ranges: Go github.com/enchant97/note-mark/backend >=0 <0.0.0-20260601210719-67b7de04308a)

Commands are suggestions: review each one before running it.

Loading voting…