Note Mark: Unauthenticated read of notes and assets in soft-deleted public books

Exploitation

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

CVSS

5.3 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

EPSS

• CVE-2026-41572: 0.24% estimated exploitation activity in the next 30 days; percentile 15.61 (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.

Summary After a note-mark owner soft-deletes a public book, its notes and uploaded assets stay readable at /api/notes/{id}, /api/notes/{id}/content, the slug URL, and the asset endpoints. Unauthenticated callers who hold the note ID or the slug path retain access. GORM's soft-delete scope does not reach the raw JOIN books ... clauses used by the note and asset queries. Details DELETE /api/books/{bookID} sets books.deletedat to the current time. The book-level endpoint starts returning 404, which matches the owner's expectation that the book is gone. The note service and asset service query notes with a raw join that does not filter books.deletedat IS NULL: GORM applies its soft-delete scope to the primary model of a query (here, notes) and to implicit Joins("Book") association clauses. It does not rewrite raw SQL passed to Joins. The soft-deleted book row keeps ispublic = true, so the WHERE ownerid = ? OR ispublic = ? clause still evaluates true for any caller on a book that was…

Published by the source

25 Apr 2026, 23:40 UTC

Last modified by the source

7 May 2026, 20:20 UTC

Source last checked

26 Oct 2026, 15:20 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-3gr9-485j-v4xf

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

# Patch Next advisory brief: CVE-2026-41572

Advisory: Note Mark: Unauthenticated read of notes and assets in soft-deleted public books
IDs: CVE-2026-41572, GHSA-3gr9-485j-v4xf
Record: https://patchnext.com/advisories/cve-2026-41572 (revision 1, source checked 26 Oct 2026, 15:20 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.3)
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-20260417132843-d1bf845a2a2d. A vendor fix does not mean a deployment is fixed.

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

## 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-3gr9-485j-v4xf (GitHub-reviewed advisory GHSA-3gr9-485j-v4xf lists affected ranges: Go github.com/enchant97/note-mark/backend >=0 <0.0.0-20260417132843-d1bf845a2a2d)

Commands are suggestions: review each one before running it.