CVE-2026-50553

HIGHPre-NVD 8.68.6—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.6 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 68% 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).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Elevated
8.6EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.6Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Note Mark is an open-source note-taking application. Prior to version 0.19.5, 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 issue has been patched in version 0.19.5.

CVSS v3
8.6
EG Score
8.6(medium)
EG Risk
55(Track*)
EG Risk 55/100SSVC: Track*

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity86% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Watch closely — could escalate to Attend.
EPSS PROB
0%
EPSS %ILE
32%
KEV
Not listed

Published

July 9, 2026

Last Modified

September 9, 2026

Advisory Details (3)

Auto-updated Sep 4, 2026
🔬 Proof of concept available. Patch available. Sources: github, github_commit, github_release.
github_release Patch Available

V0.19.5

Patch available: enchant97/note-mark v0.19.5

https://github.com/enchant97/note-mark/releases/tag/v0.19.5
github_commit Patch Available

commit 67b7de04308a (enchant97/note-mark)

Patch available: enchant97/note-mark v0.19.5 (contains commit 67b7de04308a)

https://github.com/enchant97/note-mark/commit/67b7de04308a858ef27ceff87b514067b6d667e5
github Patch Available🟡 PoC Available

Path traversal via unsanitized book/note slug in migrate export (sibling of GHSA-g49p) · Advisory · enchant97/note-mark · GitHub

https://github.com/enchant97/note-mark/security/advisories/GHSA-rqrh-8wpv-x7hh

Vendor Advisories for CVE-2026-50553(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)
PackageVulnerable rangeFixed inDependents
github.com/enchant97/note-mark/backend—0.0.0-20260601210719-67b7de04308a—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 7× in last 7d / 20× 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.

  1. 2026-09-18 19:28 UTCEPSS rescore
  2. 2026-09-18 05:37 UTCEG score recompute
  3. 2026-09-16 14:08 UTCEPSS rescore
  4. 2026-09-16 05:15 UTCEPSS rescore
  5. 2026-09-13 23:46 UTCEG score recompute
  6. 2026-09-13 16:47 UTCEPSS rescore
  7. 2026-09-12 16:41 UTCEG score recompute
  8. 2026-09-12 03:25 UTCEG score recompute
  9. 2026-09-11 14:53 UTCEPSS rescore
  10. 2026-09-10 09:35 UTCEPSS rescore
  11. 2026-09-09 22:57 UTCEG score recompute
  12. 2026-09-08 22:01 UTCEPSS rescore
  13. 2026-09-07 16:01 UTCEPSS rescore
  14. 2026-09-06 14:00 UTCEG score recompute
  15. 2026-09-06 13:47 UTCEPSS rescore
  16. 2026-09-05 22:36 UTCEG score recompute
  17. 2026-09-04 18:42 UTCEG score recompute
  18. 2026-09-04 17:55 UTCEG score recompute
  19. 2026-09-04 17:29 UTCEG score recompute▲ 8.60
  20. 2026-09-04 17:29 UTCMITRE cvelistV5CVSS v3 → 8.6 · CVSS v4 → 8.6
  21. 2026-08-01 09:12 UTCEG score recompute
  22. 2026-07-26 12:20 UTCEG score recompute
  23. 2026-07-23 03:18 UTCEG score recompute
  24. 2026-07-09 13:45 UTCEG score recompute

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-50553?
CVE-2026-50553 is a high vulnerability published on July 9, 2026. Note Mark is an open-source note-taking application. Prior to version 0.19.5, 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.…
When was CVE-2026-50553 disclosed?
CVE-2026-50553 was first published in the National Vulnerability Database on July 9, 2026, with the most recent update on September 9, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-50553 actively exploited?
CVE-2026-50553 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 68.3% of all scored CVEs.
What is the CVSS score of CVE-2026-50553?
CVE-2026-50553 has a CVSS v3 base score of 8.6 (NVD).
How do I remediate CVE-2026-50553?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-50553, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-50553

Explore →

Is Your Infrastructure Affected by CVE-2026-50553?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs