CVE-2026-44523: Github.com/enchant97/note mark/backend Note Mark Has A JWT Vulnerability

CRITICAL
Advisory Identifier: GHSA-q6mh-rqwh-g786
CVSS 10.0
CWE-345 CWE-326
Published
Advisory Summary

CVE-2026-44523 is a CRITICAL (CVSS 10.0) note mark has a jwt vulnerability (CWE-345: Insufficient Verification of Data Authenticity) affecting Github.com/enchant97/note mark/backend libraries in the Go ecosystem. The issue involves note mark has a jwt secret weakness that allows full account takeover via token forgery. Remediation is available by upgrading affected packages to version 0.0.0-20260501152247-18b587758667.

CVE-2026-44523 at a Glance

CVE Identifier CVE-2026-44523
GHSA Identifier GHSA-q6mh-rqwh-g786
Severity CRITICAL
CVSS v3.1 Base Score 10.0
CWE Classification CWE-345: Insufficient Verification of Data Authenticity
Affected Product Github.com/enchant97/note mark/backend
Package Ecosystem Go
Published Date
Last Updated

Security Impact

CVSS: 10.0

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required None (PR:N)
User Interaction None (UI:N)
Scope Changed (S:C)
Confidentiality High (C:H)
Integrity High (I:H)
Availability None (A:N)

How to Fix CVE-2026-44523

To remediate this vulnerability, upgrade all affected Github.com/enchant97/note mark/backend dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

github.com/enchant97/note-mark/backend fixed: 0.0.0-20260501152247-18b587758667
Upgrade github.com/enchant97/note-mark/backend to 0.0.0-20260501152247-18b587758667
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for github.com/enchant97/note-mark/backend

How to Check if You Are Affected

To determine whether your application is affected by CVE-2026-44523, inspect your project dependencies for Github.com/enchant97/note mark/backend:

inspect dependencies for github.com/enchant97/note-mark/backend

Analyze the terminal output to locate any version of Github.com/enchant97/note mark/backend in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 0.0.0-20260501152247-18b587758667), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-345: Insufficient Verification of Data Authenticity, where the product does not sufficiently verify the origin or authenticity of data, in a way that causes it to accept invalid data. In Github.com/enchant97/note mark/backend, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

#### Summary No minimum length or entropy is enforced on the `JWT_SECRET` configuration value. The application accepts any base64-decodable secret regardless of size, including secrets as short as 1 byte. HS256 secrets below 32 bytes are brute-forceable offline, allowing attackers to recover the signing key and forge valid JWTs for arbitrary users. --- #### Impact An attacker who captures a single valid JWT (e.g, from cookies, logs, or network traffic) can: \> Crack the signing secret offline using brute-force or wordlist attacks \> Forge valid JWTs for any user ID (including administrators) \> Authenticate without knowing any credentials This results in **full account takeover across the entire application** with no server-side detection or rate limiting possible. --- #### Details In `backend/config/utils.go`, the `Base64Decoded.UnmarshalText` function decodes the JWT secret but does not validate its length or entropy. In `backend/core/auth.go`, JWT tokens are signed using HS256 without enforcing minimum key size requirements. According to **RFC 7518 Section 3.2**, HS256 keys must be at least 256 bits (32 bytes). Libraries such as PyJWT explicitly warn against shorter keys, but note-mark performs no such validation. --- ### PoC 1- Deploy note-mark with a weak secret: ``` JWT_SECRET = base64("testsecret123456789012345") ``` 2- Register an account and capture the `Auth-Session-Token` cookie 3- Crack the secret offline (example using Python): ```python import jwt, base64 jwt.decode(TOKEN, base64.b64decode(SECRET), algorithms=["HS256"]) ``` 4- Forge a new token for any user UUID with extended expiry 5- Send the forged token in requests → server returns **200 Ok** and authenticates as that user --- ### Reproduction Steps 1- Deploy the application with a JWT secret shorter than 32 bytes (after base64 decoding) 2- Authenticate and capture a valid JWT 3- Perform offline brute-force or dictionary attack against the token signature 4- Recover the secret 5- Generate a forged JWT for another user 6- Use the forged token to access protected endpoints --- ### Fix Recommendation * Enforce a **minimum of 32 bytes (256 bits)** for JWT secrets after base64 decoding * Reject weak secrets during configuration parsing (e.g., in `Base64Decoded.UnmarshalText` or config validation) * Optionally log warnings or fail startup if the secret is insecure --- ### Resources * RFC 7518 Section 3.2 (JSON Web Algorithms - HMAC key size requirements) * CWE-326: Inadequate Encryption Strength * CWE-345: Insufficient Verification of Data Authenticity ---

CVE-2026-44523 Affected Github.com/enchant97/note mark/backend Versions

1 component(s)
Fixed Versions:
0.0.0-20260501152247-18b587758667
Product / Package Ecosystem Affected Versions Fixed Version
github.com/enchant97/note-mark/backend
Go
< 0.0.0-20260501152247-18b587758667
0.0.0-20260501152247-18b587758667

References

Frequently Asked Questions

What is CVE-2026-44523?
CVE-2026-44523 is a security vulnerability in Github.com/enchant97/note mark/backend involving Note Mark has a JWT Secret Weakness that allows Full Account Takeover via Token Forgery under CWE-345: Insufficient Verification of Data Authenticity.
Which Github.com/enchant97/note mark/backend versions are affected?
Affected versions include releases prior to 0.0.0-20260501152247-18b587758667 across affected packages: github.com/enchant97/note-mark/backend.
What version fixes CVE-2026-44523?
Upgrading to 0.0.0-20260501152247-18b587758667 (or the latest patched release for your respective branch) resolves the vulnerability.
Is github.com/enchant97/note-mark/backend affected?
Yes, github.com/enchant97/note-mark/backend is affected in releases prior to 0.0.0-20260501152247-18b587758667. Upgrade your dependency to 0.0.0-20260501152247-18b587758667 or later.
What is the CVSS score of CVE-2026-44523?
CVE-2026-44523 has a CVSS v3.1 base score of 10.0 (CRITICAL) with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N.
What CWE is associated with CVE-2026-44523?
CVE-2026-44523 is classified under CWE-345: Insufficient Verification of Data Authenticity (The product does not sufficiently verify the origin or authenticity of data, in a way that causes it to accept invalid data.).
How can I check Go dependencies for CVE-2026-44523?
Run the dependency tree command: 'inspect dependencies for github.com/enchant97/note-mark/backend'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-q6mh-rqwh-g786",
  "modified" : "2026-05-15T23:45:05Z",
  "published" : "2026-05-07T21:08:10Z",
  "aliases" : [ "CVE-2026-44523" ],
  "summary" : "Note Mark has a JWT Secret Weakness that allows Full Account Takeover via Token Forgery",
  "details" : "#### Summary\n\nNo minimum length or entropy is enforced on the `JWT_SECRET` configuration value. The application accepts any base64-decodable secret regardless of size, including secrets as short as 1 byte.\n\nHS256 secrets below 32 bytes are brute-forceable offline, allowing attackers to recover the signing key and forge valid JWTs for arbitrary users.\n\n---\n\n#### Impact\n\nAn attacker who captures a single valid JWT (e.g, from cookies, logs, or network traffic) can:\n\n\\> Crack the signing secret offline using brute-force or wordlist attacks\n\\> Forge valid JWTs for any user ID (including administrators)\n\\> Authenticate without knowing any credentials\n\nThis results in **full account takeover across the entire application** with no server-side detection or rate limiting possible.\n\n---\n\n#### Details\n\nIn `backend/config/utils.go`, the `Base64Decoded.UnmarshalText` function decodes the JWT secret but does not validate its length or entropy.\n\nIn `backend/core/auth.go`, JWT tokens are signed using HS256 without enforcing minimum key size requirements.\n\nAccording to **RFC 7518 Section 3.2**, HS256 keys must be at least 256 bits (32 bytes). Libraries such as PyJWT explicitly warn against shorter keys, but note-mark performs no such validation.\n\n---\n\n### PoC\n\n1- Deploy note-mark with a weak secret:\n\n   ```\n   JWT_SECRET = base64(\"testsecret123456789012345\")\n   ```\n\n2- Register an account and capture the `Auth-Session-Token` cookie\n\n3- Crack the secret offline (example using Python):\n\n   ```python\n   import jwt, base64\n   jwt.decode(TOKEN, base64.b64decode(SECRET), algorithms=[\"HS256\"])\n   ```\n\n4- Forge a new token for any user UUID with extended expiry\n\n5- Send the forged token in requests → server returns **200 Ok** and authenticates as that user\n\n---\n\n### Reproduction Steps\n\n1- Deploy the application with a JWT secret shorter than 32 bytes (after base64 decoding)\n2- Authenticate and capture a valid JWT\n3- Perform offline brute-force or dictionary attack against the token signature\n4- Recover the secret\n5- Generate a forged JWT for another user\n6- Use the forged token to access protected endpoints\n\n---\n\n### Fix Recommendation\n\n* Enforce a **minimum of 32 bytes (256 bits)** for JWT secrets after base64 decoding\n* Reject weak secrets during configuration parsing (e.g., in `Base64Decoded.UnmarshalText` or config validation)\n* Optionally log warnings or fail startup if the secret is insecure\n\n---\n\n### Resources\n\n* RFC 7518 Section 3.2 (JSON Web Algorithms - HMAC key size requirements)\n* CWE-326: Inadequate Encryption Strength\n* CWE-345: Insufficient Verification of Data Authenticity\n\n---",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/enchant97/note-mark/backend"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "0.0.0-20260501152247-18b587758667"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/enchant97/note-mark/security/advisories/GHSA-q6mh-rqwh-g786"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-44523"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/enchant97/note-mark/commit/18b58775866776ed400c403dd0ccad68c1fa4802"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/enchant97/note-mark"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/enchant97/note-mark/releases/tag/v0.19.4"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-326", "CWE-345" ],
    "severity" : "CRITICAL",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-05-07T21:08:10Z",
    "nvd_published_at" : "2026-05-14T19:16:37Z"
  }
}