CVE-2026-53603: forgekeep nebula-mesh plaintext storage of operator session tokens

CVE-2026-53603 · Severity: high · CVSS 4 · Published 2026-09-04

Nebula-mesh is a tool used for managing network overlays. A security flaw was identified where operator session tokens—the digital keys used to maintain a logged-in session—were stored in the database in plain text. If an attacker gains access to database backups or snapshots, they can use these tokens to impersonate legitimate administrators and take full control of the system without needing a password.

Technologies: Forgekeep Nebula-Mesh, github.com/forgekeep/nebula-mesh (Go). Vendors: Forgekeep, Go.

Quick answers

Is CVE-2026-53603 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-53603 being exploited in the wild.
How severe is CVE-2026-53603?
High severity, with a CVSS score of 4, published 4 September 2026.
Which products and versions are affected?
github.com/forgekeep/nebula-mesh (Go) <= 0.3.7, SEMVER:introduced=0,fixed=0.3.8.
Is there a fix for CVE-2026-53603?
Yes. github.com/forgekeep/nebula-mesh (Go): upgrade to 0.3.8 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-53603 attacked?
It is attacked over the network, in a software library.
Am I affected by CVE-2026-53603?
Check whether you run Forgekeep Nebula-Mesh or github.com/forgekeep/nebula-mesh (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • github.com/forgekeep/nebula-mesh (Go): upgrade to 0.3.8 or later
    go get github.com/forgekeep/nebula-mesh@v0.3.8

Technical details

A vulnerability in nebula-mesh (specifically within the operator session management logic) results in session tokens being stored in plaintext in the 'operator_sessions' table. The session token, a 32-byte random hex value, is used as a primary key and is sent via cookies for authentication. An attacker with read access to the database—via SQL injection, insecure backups, or file system access—can retrieve these tokens to bypass authentication and hijack active operator sessions. The root cause is the lack of hashing for session tokens, unlike API keys and enrollment tokens in the same application. This issue is addressed in version 0.3.8 by implementing SHA-256 hashing for session tokens at rest.

Affected products

  • forgekeep nebula-mesh <= 0.3.7

Identifiers

  • CVE-2026-53603
  • GHSA-q4vm-pq3q-8wgq
  • GO-2026-5991

Timeline

  • 2026-06-04: disclosed: Initial report and commit fix
  • 2026-07-14: advisory: GitHub Advisory published
  • 2026-07-14: patched: Version 0.3.8 released

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.