CVE-2026-40263: Note Mark Username Enumeration Vulnerability

LOW
Advisory Identifier: GHSA-w6m9-39cv-2fwp
CVSS 3.7
CWE-208
Published
Advisory Summary

CVE-2026-40263 is a LOW (CVSS 3.7) username enumeration vulnerability (CWE-208: Observable Timing Discrepancy) affecting Note Mark libraries in the Go ecosystem. The issue involves username enumeration via login endpoint timing side-channel. Remediation is available by upgrading affected packages to version 0.19.2-0.20260411145025-cf4c6f6acf70.

CVE-2026-40263 at a Glance

CVE Identifier CVE-2026-40263
GHSA Identifier GHSA-w6m9-39cv-2fwp
Severity LOW
CVSS v3.1 Base Score 3.7
CWE Classification CWE-208: Observable Timing Discrepancy
Affected Product Note Mark
Package Ecosystem Go
Published Date
Last Updated

Security Impact

CVSS: 3.7

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

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

How to Fix CVE-2026-40263

To remediate this vulnerability, upgrade all affected Note Mark 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.19.2-0.20260411145025-cf4c6f6acf70
Upgrade github.com/enchant97/note-mark/backend to 0.19.2-0.20260411145025-cf4c6f6acf70
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-40263, inspect your project dependencies for Note Mark:

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

Analyze the terminal output to locate any version of Note Mark in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 0.19.2-0.20260411145025-cf4c6f6acf70), 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-208: Observable Timing Discrepancy, where two separate operations in a product require different amounts of time to complete, in a way that is observable to an actor and reveals security-relevant information about the state of the product, such as whether a particular operation was successful or not. In Note Mark, 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 A timing side-channel in the login endpoint allows unauthenticated attackers to determine whether a username exists by measuring response time differences. Requests for valid usernames take noticeably longer because the server performs bcrypt password verification, while requests for nonexistent usernames return much faster. This enables reliable remote username enumeration and increases the risk of targeted credential attacks. ### Details The issue affects the login endpoint: - `POST /api/auth/token` The root cause is that authentication processing takes different code paths depending on whether the supplied username exists. When the username is found, the server performs `bcrypt.CompareHashAndPassword`, which adds substantial latency. When the username does not exist, the server returns immediately without performing an equivalent bcrypt operation. Vulnerable flow: ```go user, err := db.Where("username = ?", username).First(&user) if err != nil { return ErrUnauthorized } err = bcrypt.CompareHashAndPassword(user.PasswordHash, []byte(password)) ``` This creates a measurable timing discrepancy between: - **existing username + wrong password** requests, which incur bcrypt cost - **nonexistent username + any password** requests, which avoid bcrypt entirely Because no constant-time equalization is performed, the endpoint leaks account existence through timing behavior. The measurements provided show a large and consistent gap between the two cases across repeated trials, making the difference distinguishable without requiring especially high request volume. In the supplied test results: - existing user requests averaged about `0.0616s` - nonexistent user requests averaged about `0.0027s` That gap is large enough to support reliable username enumeration under typical testing conditions. ### PoC The issue can be reproduced by sending repeated authentication attempts to the login endpoint using the same invalid password while alternating between a known valid username and a nonexistent username, then comparing average response times. Valid usernames consistently take longer because bcrypt verification is performed. ### Impact - **Type:** Timing side-channel / username enumeration - **Who is impacted:** Any deployment exposing the affected login endpoint - **Security impact:** Unauthenticated attackers can confirm valid usernames one at a time, improving the effectiveness of credential stuffing, password spraying, phishing, and other targeted account attacks - **Attack preconditions:** None beyond network access to the login endpoint - **Confidentiality impact:** Low to moderate, depending on the sensitivity of account existence in the target environment

CVE-2026-40263 Affected Note Mark Versions

1 component(s)
Fixed Versions:
0.19.2-0.20260411145025-cf4c6f6acf70
Product / Package Ecosystem Affected Versions Fixed Version
github.com/enchant97/note-mark/backend
Go
< 0.19.2-0.20260411145025-cf4c6f6acf70
0.19.2-0.20260411145025-cf4c6f6acf70

References

Frequently Asked Questions

What is CVE-2026-40263?
CVE-2026-40263 is a security vulnerability in Note Mark involving Username Enumeration via Login Endpoint Timing Side-Channel under CWE-208: Observable Timing Discrepancy.
Which Note Mark versions are affected?
Affected versions include releases prior to 0.19.2-0.20260411145025-cf4c6f6acf70 across affected packages: github.com/enchant97/note-mark/backend.
What version fixes CVE-2026-40263?
Upgrading to 0.19.2-0.20260411145025-cf4c6f6acf70 (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.19.2-0.20260411145025-cf4c6f6acf70. Upgrade your dependency to 0.19.2-0.20260411145025-cf4c6f6acf70 or later.
What is the CVSS score of CVE-2026-40263?
CVE-2026-40263 has a CVSS v3.1 base score of 3.7 (LOW) with vector string CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N.
What CWE is associated with CVE-2026-40263?
CVE-2026-40263 is classified under CWE-208: Observable Timing Discrepancy (Two separate operations in a product require different amounts of time to complete, in a way that is observable to an actor and reveals security-relevant information about the state of the product, such as whether a particular operation was successful or not.).
How can I check Go dependencies for CVE-2026-40263?
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-w6m9-39cv-2fwp",
  "modified" : "2026-04-24T20:37:10Z",
  "published" : "2026-04-13T19:31:50Z",
  "aliases" : [ "CVE-2026-40263" ],
  "summary" : "Note Mark: Username Enumeration via Login Endpoint Timing Side-Channel",
  "details" : "### Summary\nA timing side-channel in the login endpoint allows unauthenticated attackers to determine whether a username exists by measuring response time differences. Requests for valid usernames take noticeably longer because the server performs bcrypt password verification, while requests for nonexistent usernames return much faster. This enables reliable remote username enumeration and increases the risk of targeted credential attacks.\n\n### Details\nThe issue affects the login endpoint:\n\n- `POST /api/auth/token`\n\nThe root cause is that authentication processing takes different code paths depending on whether the supplied username exists. When the username is found, the server performs `bcrypt.CompareHashAndPassword`, which adds substantial latency. When the username does not exist, the server returns immediately without performing an equivalent bcrypt operation.\n\nVulnerable flow:\n\n```go\nuser, err := db.Where(\"username = ?\", username).First(&user)\nif err != nil {\n    return ErrUnauthorized\n}\nerr = bcrypt.CompareHashAndPassword(user.PasswordHash, []byte(password))\n```\n\nThis creates a measurable timing discrepancy between:\n- **existing username + wrong password** requests, which incur bcrypt cost\n- **nonexistent username + any password** requests, which avoid bcrypt entirely\n\nBecause no constant-time equalization is performed, the endpoint leaks account existence through timing behavior.\n\nThe measurements provided show a large and consistent gap between the two cases across repeated trials, making the difference distinguishable without requiring especially high request volume. In the supplied test results:\n- existing user requests averaged about `0.0616s`\n- nonexistent user requests averaged about `0.0027s`\n\nThat gap is large enough to support reliable username enumeration under typical testing conditions.\n\n### PoC\nThe issue can be reproduced by sending repeated authentication attempts to the login endpoint using the same invalid password while alternating between a known valid username and a nonexistent username, then comparing average response times. Valid usernames consistently take longer because bcrypt verification is performed.\n\n### Impact\n- **Type:** Timing side-channel / username enumeration\n- **Who is impacted:** Any deployment exposing the affected login endpoint\n- **Security impact:** Unauthenticated attackers can confirm valid usernames one at a time, improving the effectiveness of credential stuffing, password spraying, phishing, and other targeted account attacks\n- **Attack preconditions:** None beyond network access to the login endpoint\n- **Confidentiality impact:** Low to moderate, depending on the sensitivity of account existence in the target environment",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/enchant97/note-mark/backend"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "0.19.2-0.20260411145025-cf4c6f6acf70"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/enchant97/note-mark/security/advisories/GHSA-w6m9-39cv-2fwp"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-40263"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/enchant97/note-mark/commit/cf4c6f6acf70b569d80396d323b067c00d45c034"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/enchant97/note-mark"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-208" ],
    "severity" : "LOW",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-04-13T19:31:50Z",
    "nvd_published_at" : "2026-04-17T01:17:40Z"
  }
}