# CVE-2026-50554: Note Mark: Unauthenticated disclosure of soft-deleted note metadata via deleted=true on public books in note-mark

> Unauthenticated attackers can view metadata of soft-deleted notes in public books by exploiting an API parameter that bypasses soft-delete scoping.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 3 Sep 2026
- **Updated:** 3 Sep 2026
- **Also known as:** GHSA-588f-fvcv-xhvf, GO-2026-5948

## What is CVE-2026-50554?

CVE-2026-50554 is a medium-severity vulnerability in enchant97 note-mark, published on 3 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Note Mark is an open-source note-taking application. Prior to version 0.19.5, GET /api/books/{bookID}/notes is an unauthenticated endpoint that accepts a "deleted" query parameter. When the request is ?deleted=true, the service runs the query with Unscoped() (bypassing GORM's soft-delete scope) but keeps the read-authorization clause as "owner_id = ? OR is_public = ?". As a result, any unauthenticated caller can enumerate the metadata of soft-deleted ("trashed") notes belonging to any public book — notes the owner explicitly deleted and expected to be removed from public view. This issue has been patched in version 0.19.5.

Weakness: CWE-285 (Improper Authorization), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2026-50554?

3 open source packages ship an affected version, including github.com/enchant97/note-mark/backend.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/enchant97/note-mark/backend` | Go | All versions | 0.0.0-20260601210758-9c9b72740f22 |
| `github.com/enchant97/note-mark/backend` | Go | All versions | 0.0.0-20260601210758-9c9b72740f22 |
| `github.com/enchant97/note-mark/backend` | Go | All versions | 0.0.0-20260601210758-9c9b72740f22 |

## How do I fix CVE-2026-50554?

Upgrade github.com/enchant97/note-mark/backend to 0.0.0-20260601210758-9c9b72740f22 or later.

## Is CVE-2026-50554 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-50554 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-50554 and fix it if it is affected.

What it is: CVE-2026-50554 is a medium-severity vulnerability in enchant97 note-mark, published on 3 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-50554 exists.

Affected packages and fixed versions:
- github.com/enchant97/note-mark/backend (Go): affected all versions; fixed in 0.0.0-20260601210758-9c9b72740f22
- github.com/enchant97/note-mark/backend (Go): affected all versions; fixed in 0.0.0-20260601210758-9c9b72740f22
- github.com/enchant97/note-mark/backend (Go): affected all versions; fixed in 0.0.0-20260601210758-9c9b72740f22

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-50554/ (Markdown: https://insights.sbomify.com/CVE-2026-50554/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-50554
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-50554
- OSV: https://osv.dev/vulnerability/CVE-2026-50554

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-50554/
Summaries are generated and may contain mistakes; the official description above is the record.