Vulnerability in github.com/enchant97/note-mark/backend (CVE-2026-44522)
Summary
Vulnerability in github.com/enchant97/note-mark/backend (CVE-2026-44522). Risk of unauthorized operations or information disclosure. Exploitable via POST /api/notes/{noteID}/assets. Mitigation: upgrade to 0.0.0-20260501152243-db3f72bff780 or later.
Original description
The description as published by the source.
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.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-44522 has been found in github.com/enchant97/note-mark/backend.
Attackers can target a specific entry point like POST /api/notes/{noteID}/assets over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade github.com/enchant97/note-mark/backend to 0.0.0-20260501152243-db3f72bff780 or later.
If unsure, ask your IT team or search "github.com/enchant97/note-mark/backend CVE-2026-44522" on the vendor's site.
CVE-2026-44522 (github.com/enchant97/note-mark/backend) — CWE-20
Attack surface: POST /api/notes/{noteID}/assets / note_assets / Name / bash
Patched: 0.0.0-20260501152243-db3f72bff780 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-20) exists in github.com/enchant97/note-mark/backend. Attackers reach the vulnerable code path via POST /api/notes/{noteID}/assets.
Check the vendor advisory for the affected versions of github.com/enchant97/note-mark/backend. Attack surface: POST /api/notes/{noteID}/assets / note_assets / Name / bash.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 0.0.0-20260501152243-db3f72bff780.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual POST /api/notes/{noteID}/assets requests with malformed payloads or SQL meta-characters. Run grep -r 'github.com/enchant97/note-mark/backend' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'github.com/enchant97/note-mark/backend' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
github.com/enchant97/note-mark/backendを grep し、稼働しているサービス・バージョンを把握する。 -
2Hunt for indicators of compromise detect
grep 'POST /api/notes/{noteID}/assets' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
POST /api/notes/{noteID}/assetsへの異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Apply patch patch
Upgrade github.com/enchant97/note-mark/backend to 0.0.0-20260501152243-db3f72bff780ステージング環境で 0.0.0-20260501152243-db3f72bff780 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。
-
4Post-deployment verification verify
Replay attack against POST /api/notes/{noteID}/assets on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- web github.com
- web github.com