Advisory record · GHSA-q6mh-rqwh-g786

Note Mark has a JWT Secret Weakness that allows Full Account Takeover via Token Forgery

CVSS 10.0 CriticalCriticalEPSS 0.0015 · 4th percentile

Critical, because:

  • CVSS score 10.0: 9.0 or more.

How we decide what’s critical

Published by the GitHub Advisory Database at 7 May 2026, 21:08 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
github.com/enchant97/note-mark/backendGo<0.0.0-20260501152247-18b5877586670.0.0-20260501152247-18b587758667
Identifiers
GHSA-q6mh-rqwh-g786 · CVE-2026-44523 · GO-2026-5567
Weakness (CWE)
CWE-326 · CWE-345
Published
7 May 2026
Updated
25 Jun 2026

Machine-written summary

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

Note Mark (github.com/enchant97/note-mark/backend) accepts any JWT_SECRET value, including very short ones, so the signing key can be brute-forced offline. An attacker who captures one valid JWT could recover the secret, forge tokens for any user, and take over accounts without credentials. The fixed version is 0.0.0-20260501152247-18b587758667, and versions before it are affected; upgrade to that version. The source lists no workaround, though setting a JWT secret of at least 32 bytes avoids the weakness.

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

ScoreRatingCVSSVectorSource
10.0 Critical 3.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0015, the 4th percentile, on 9 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 15:06 UTC First seen by agentprime
  2. 31 Oct 2026, 15:06 UTC Confirmed by OSV

Sources

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.