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

Advisory record · `GHSA-3gr9-485j-v4xf`

- **Identifiers:** `GHSA-3gr9-485j-v4xf` · `CVE-2026-41572` · `GO-2026-5085`
- **State:** Confirmed
- **Severity:** CVSS 5.3 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-285](https://cwe.mitre.org/data/definitions/285.html)
- **Tags:** [Broken access control](https://agentprime.io/advisories/tag/access-control.md)
- **Published:** 25 Apr 2026
- **Updated:** 25 Jun 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 25 Apr 2026, 23:40 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `github.com/enchant97/note-mark/backend` (Go): affected `<0.0.0-20260417132843-d1bf845a2a2d`; fixed in `0.0.0-20260417132843-d1bf845a2a2d`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Note Mark (Go module github.com/enchant97/note-mark/backend) versions up to and including 0.0.0-20260417132843-d1bf845a2a2d are affected. When a public book is soft-deleted, its notes and assets remain readable without authentication through note and asset endpoints if the caller knows the note ID or slug. The fix is listed as 0.0.0-20260417132843-d1bf845a2a2d, so users should upgrade to that version. The source gives no other workaround.

Written 7 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 5.3 Medium, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0024, the 15th percentile, on 18 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 15:07 UTC: First seen by agentprime
- 31 Oct 2026, 15:07 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-3gr9-485j-v4xf)

## Sources

- [GitHub Advisory Database: GHSA-3gr9-485j-v4xf](https://github.com/advisories/GHSA-3gr9-485j-v4xf)
- [OSV: GHSA-3gr9-485j-v4xf](https://osv.dev/vulnerability/GHSA-3gr9-485j-v4xf)
- <https://github.com/enchant97/note-mark/security/advisories/GHSA-3gr9-485j-v4xf>
- <https://nvd.nist.gov/vuln/detail/CVE-2026-41572>
- <https://github.com/enchant97/note-mark/commit/d1bf845a2a2df01e2eca6f556287db4ec6f773cf>
- <https://github.com/enchant97/note-mark>
- <https://github.com/enchant97/note-mark/releases/tag/v0.19.3>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-3gr9-485j-v4xf>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-3gr9-485j-v4xf/>. Everything for agents: <https://agentprime.io/llms.txt>.
