Skip to content

Instantly share code, notes, and snippets.

@L4wCat
Last active August 5, 2026 10:40
Show Gist options
  • Select an option

  • Save L4wCat/924c10c36d6d11651049787d547d411b to your computer and use it in GitHub Desktop.

Select an option

Save L4wCat/924c10c36d6d11651049787d547d411b to your computer and use it in GitHub Desktop.
[CVE-2026-52111] Fast Note Sync Service Arbitrary User Login Vulnerability

Fast Note Sync Service Arbitrary User Login Vulnerability

MITRE form fields

CVE ID

CVE-2026-52111

Public URL

https://github.com/haierkeys/fast-note-sync-service/issues/268

Other details (optional)

The referenced public issue describes an authentication and authorization vulnerability chain in Fast Note Sync Service. Under the affected Docker deployment conditions, a remote attacker can self-register a normal account, bypass the administrator authorization check, obtain JWT signing material from an administrative configuration endpoint, and forge a token for an arbitrary user identifier when the machine identifier is empty, known, or predictable. Successful exploitation can result in arbitrary user impersonation, administrator account takeover, and unauthorized reading, modification, or deletion of synchronized notes and metadata.

Suggested CWE: CWE-863 (Incorrect Authorization), with CWE-321 (Use of Hard-coded Cryptographic Key) as a secondary weakness.

Suggested CVSS v4.0: 9.2 Critical
Vector: CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

The exact affected-version and fixed-version ranges have not been confirmed by the project maintainer.

Public advisory

Summary

Fast Note Sync Service contains an authentication and authorization vulnerability chain that may allow a remote attacker to impersonate arbitrary users, including an administrator.

In the affected Docker deployment scenario, an attacker can register a normal account, bypass an administrator authorization check, retrieve JWT signing material from an administrative configuration endpoint, and forge a JWT for another user when the machine identifier is empty, known, or predictable.

Preconditions

The reported exploitation path requires:

  • User registration to be enabled.
  • The service to be deployed using Docker.
  • The affected administrator authorization behavior to be present.
  • The administrative configuration endpoint to expose JWT signing material.
  • The machine identifier to be empty, known, or predictable.

Root cause

The public report identifies the following vulnerability chain:

  1. Anonymous users can self-register.
  2. An admin-uid value of 0 causes an incorrect administrator authorization result.
  3. An administrative configuration endpoint exposes authTokenKey.
  4. User JWTs are signed using authTokenKey + "_" + machine_id.
  5. In the affected Docker path, machine_id may be empty, known, or predictable.
  6. The exposed signing material can then be used to impersonate another user identifier.

Impact

Successful exploitation may result in:

  • Arbitrary user impersonation.
  • Administrator account takeover.
  • Unauthorized access to private notes and metadata.
  • Modification or deletion of synchronized content.

CWE

  • CWE-863 — Incorrect Authorization
  • CWE-321 — Use of Hard-coded Cryptographic Key (secondary)

CVSS

Suggested CVSS v4.0 score: 9.2 — Critical

CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

The score is a researcher assessment and may be adjusted by the assigning CNA, MITRE, or NVD.

Affected versions

The exact affected-version range has not been confirmed by the project maintainer. Avoid claiming a precise version range until the maintainer or assigning CNA confirms it.

Recommended remediation

  • Upgrade to a maintainer-confirmed fixed release.
  • Disable public registration when it is not required.
  • Correct the administrator authorization check and safely reject zero or unset administrator identifiers.
  • Do not expose authentication keys or other secrets through configuration APIs.
  • Generate a unique cryptographically random signing key for each installation.
  • Rotate the signing key and invalidate existing sessions after applying the fix.
  • Treat machine identifiers as non-secret metadata rather than cryptographic key material.

References

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment