# CVE-2026-41572: Note Mark: Unauthenticated read of notes and assets in soft-deleted public books

> Unauthenticated attackers can read notes and assets from soft-deleted public books in Note Mark due to missing authorization checks in API endpoints.

- **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:** 4 May 2026
- **Updated:** 4 May 2026
- **Also known as:** GHSA-3gr9-485j-v4xf, GO-2026-5085

## What is CVE-2026-41572?

CVE-2026-41572 is a medium-severity missing authorization vulnerability in enchant97 note-mark, published on 4 May 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.3, 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. This issue has been patched in version 0.19.3.

Weakness: CWE-285 (Improper Authorization)

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

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-20260417132843-d1bf845a2a2d |
| `github.com/enchant97/note-mark/backend` | Go | All versions | 0.0.0-20260417132843-d1bf845a2a2d |
| `github.com/enchant97/note-mark/backend` | Go | All versions | 0.0.0-20260417132843-d1bf845a2a2d |

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

Upgrade github.com/enchant97/note-mark/backend to 0.0.0-20260417132843-d1bf845a2a2d or later.

## Is CVE-2026-41572 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-41572 is a medium-severity missing authorization vulnerability in enchant97 note-mark, published on 4 May 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-41572 exists.

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

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-41572/ (Markdown: https://insights.sbomify.com/CVE-2026-41572/index.md)
```

## Sources

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

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