← Back
CVE-2026-41572
Vulnerability in github.com/enchant97/note-mark/backend (CVE-2026-41572)
Summary
vulnerability in github.com/enchant97/note-mark/backend (CVE-2026-41572). Risk of unauthorized operations or information disclosure. Exploitable via `DELETE /api/books/{bookID}`. Mitigation: upgrade to `0.0.0-20260417132843-d1bf845a2a2d` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-41572** has been found in github.com/enchant97/note-mark/backend.
Attackers can target a specific entry point like `DELETE /api/books/{bookID}` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: upgrade github.com/enchant97/note-mark/backend to **0.0.0-20260417132843-d1bf845a2a2d** or later.
If unsure, ask your IT team or search "github.com/enchant97/note-mark/backend CVE-2026-41572" on the vendor's site.
CVE-2026-41572 (github.com/enchant97/note-mark/backend) — CWE-285 /
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: DELETE /api/books/{bookID} / PUT /api/notes/{noteID}/restore / PUT /api/notes/{id}/restore / `books.deleted_at`
Patched: `0.0.0-20260417132843-d1bf845a2a2d` — 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.
❓ What is the problem
**A vulnerability** (CWE-285) exists in github.com/enchant97/note-mark/backend. Attackers reach the vulnerable code path via `DELETE /api/books/{bookID}` without authentication.
📍 Affected scope
github.com/enchant97/note-mark/backend — . Attack surface: DELETE /api/books/{bookID} / PUT /api/notes/{noteID}/restore / PUT /api/notes/{id}/restore / `books.deleted_at`.
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **0.0.0-20260417132843-d1bf845a2a2d**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual `DELETE /api/books/{bookID}` 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 (7 steps)
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 し、稼働しているサービス・バージョンを把握する。
-
3Hunt for indicators of compromise detect
grep 'DELETE /api/books/{bookID}' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで `DELETE /api/books/{bookID}` への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。
-
6Apply patch patch
Upgrade github.com/enchant97/note-mark/backend to 0.0.0-20260417132843-d1bf845a2a2dステージング環境で 0.0.0-20260417132843-d1bf845a2a2d に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Replay attack against DELETE /api/books/{bookID} on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
Go
github.com/enchant97/note-mark/backend
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"0.0.0-20260417132843-d1bf845a2a2d"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2026-41572
- package https://github.com/enchant97/note-mark
- web https://github.com/enchant97/note-mark/security/advisories/GHSA-3gr9-485j-v4xf
- web https://github.com/enchant97/note-mark/commit/d1bf845a2a2df01e2eca6f556287db4ec6f773cf
- web https://github.com/enchant97/note-mark/releases/tag/v0.19.3