Note Mark has Broken Access Control on Asset Download

Exploitation

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

CVSS

5.9 · CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N

EPSS

• CVE-2026-40265: 0.44% estimated exploitation activity in the next 30 days; percentile 38.35 (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 A broken access control vulnerability allows unauthenticated users to retrieve note assets directly from the asset download endpoint when they know both the note UUID and asset UUID. This exposes the full contents of private note assets without authentication, even when the associated book is not public. Details The issue is caused by the asset download route being registered without authentication middleware. Relevant route registration: - handlers/assets.go, line 40 By contrast, other asset operations correctly apply authentication middleware. For example: The backend service for asset retrieval also does not enforce ownership or visibility checks. According to the provided code references, the lookup only queries the asset table by asset ID and note ID: Because the retrieval path does not join against the related notes or books records, it does not verify: - whether the requester owns the parent book - whether the parent book is public or private - whether the related note…

Published by the source

13 Apr 2026, 19:31 UTC

Last modified by the source

24 Apr 2026, 20:38 UTC

Source last checked

26 Oct 2026, 15:19 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-p5w6-75f9-cc2p

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

# Patch Next advisory brief: CVE-2026-40265

Advisory: Note Mark has Broken Access Control on Asset Download
IDs: CVE-2026-40265, GHSA-p5w6-75f9-cc2p
Record: https://patchnext.com/advisories/cve-2026-40265 (revision 1, source checked 26 Oct 2026, 15:19 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.9)
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-20260411145023-6593898855ad. A vendor fix does not mean a deployment is fixed.

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

## 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-p5w6-75f9-cc2p (GitHub-reviewed advisory GHSA-p5w6-75f9-cc2p lists affected ranges: Go github.com/enchant97/note-mark/backend >=0 <0.0.0-20260411145023-6593898855ad)

Commands are suggestions: review each one before running it.