Backend: Note Mark: Unauthenticated disclosure of soft-deleted note metadata via deleted=true on public books (CVE-2026-50554)
An unauthenticated API endpoint in the Note Mark backend allows disclosure of metadata for soft-deleted (trashed) notes belonging to public books. The endpoint GET /api/books/{bookID}/notes accepts a 'deleted=true' query parameter that bypasses the soft-delete filter but still permits access if the book is public. This results in exposure of note metadata such as id, title, slug, and timestamps to unauthenticated users, even though the note owner intended these notes to be hidden. The note content itself is not exposed. The vulnerability arises from improper authorization logic that does not restrict soft-deleted notes to their owners only. A code fix involves restricting soft-deleted note listings exclusively to the book owner, preventing public access to trashed notes.
AI Analysis
Technical Summary
The Note Mark backend's GET /api/books/{bookID}/notes endpoint is unauthenticated and accepts a 'deleted' query parameter. When 'deleted=true', the query uses an unscoped database call that bypasses the soft-delete filter but retains an authorization clause allowing access if the book is public or owned by the requester. Because the endpoint lacks authentication, unauthenticated users can enumerate metadata of soft-deleted notes on public books. The note content endpoint does not expose soft-deleted notes, limiting impact to metadata disclosure. The root cause is improper authorization logic that does not restrict soft-deleted notes to owners only. The recommended fix is to modify the authorization check so that when 'deleted=true', only the owner can access the notes, effectively blocking unauthenticated access to trashed notes.
Potential Impact
Exposure of metadata (id, title, slug, timestamps) for soft-deleted notes on public books to unauthenticated actors. The note content remains protected and inaccessible for soft-deleted notes. This bypasses the intended semantics of deletion, potentially revealing information the owner expected to be hidden. There is no impact on note integrity or availability, only metadata confidentiality is affected.
Mitigation Recommendations
No official patch or fix is currently published. Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. The recommended code change is to restrict soft-deleted note listings to the book owner only, removing the 'is_public' condition when 'deleted=true'. This prevents unauthenticated users from accessing trashed note metadata. Until a fix is released, avoid exposing soft-deleted notes via unauthenticated endpoints or implement access controls restricting this data to authenticated owners.
Backend: Note Mark: Unauthenticated disclosure of soft-deleted note metadata via deleted=true on public books (CVE-2026-50554)
Description
An unauthenticated API endpoint in the Note Mark backend allows disclosure of metadata for soft-deleted (trashed) notes belonging to public books. The endpoint GET /api/books/{bookID}/notes accepts a 'deleted=true' query parameter that bypasses the soft-delete filter but still permits access if the book is public. This results in exposure of note metadata such as id, title, slug, and timestamps to unauthenticated users, even though the note owner intended these notes to be hidden. The note content itself is not exposed. The vulnerability arises from improper authorization logic that does not restrict soft-deleted notes to their owners only. A code fix involves restricting soft-deleted note listings exclusively to the book owner, preventing public access to trashed notes.
CVSS v3.1
Score 5.3medium
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The Note Mark backend's GET /api/books/{bookID}/notes endpoint is unauthenticated and accepts a 'deleted' query parameter. When 'deleted=true', the query uses an unscoped database call that bypasses the soft-delete filter but retains an authorization clause allowing access if the book is public or owned by the requester. Because the endpoint lacks authentication, unauthenticated users can enumerate metadata of soft-deleted notes on public books. The note content endpoint does not expose soft-deleted notes, limiting impact to metadata disclosure. The root cause is improper authorization logic that does not restrict soft-deleted notes to owners only. The recommended fix is to modify the authorization check so that when 'deleted=true', only the owner can access the notes, effectively blocking unauthenticated access to trashed notes.
Potential Impact
Exposure of metadata (id, title, slug, timestamps) for soft-deleted notes on public books to unauthenticated actors. The note content remains protected and inaccessible for soft-deleted notes. This bypasses the intended semantics of deletion, potentially revealing information the owner expected to be hidden. There is no impact on note integrity or availability, only metadata confidentiality is affected.
Mitigation Recommendations
No official patch or fix is currently published. Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. The recommended code change is to restrict soft-deleted note listings to the book owner only, removing the 'is_public' condition when 'deleted=true'. This prevents unauthenticated users from accessing trashed note metadata. Until a fix is released, avoid exposing soft-deleted notes via unauthenticated endpoints or implement access controls restricting this data to authenticated owners.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-588f-fvcv-xhvf
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-50554"]
- Ecosystems
- ["Go"]
- Database Specific Severity
- MODERATE
- Cvss Version
- 3.1
Threat ID: 6a50bac868715ace435892b8
Added to database: 07/10/2026, 09:26:32 UTC
Last enriched: 07/10/2026, 10:25:21 UTC
Last updated: 07/31/2026, 12:27:30 UTC
Views: 67
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.