nebula-mesh's stores enrollment tokens unhashed in SQLite

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

5.0 · CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:H/VA:N/SC:N/SI:N/SA:N/E:U · score source

EPSS

No dated EPSS signal available.

As published by the source; long descriptions are shortened.

internal/store/sqlite.go:1177,1192,1221,1245 — the enrollmenttokens.token column holds the raw UUID token. ConsumeToken does WHERE token = ? against the raw string. Compare with operatorapikeys.keyhash, which is SHA-256 hex (constructed in internal/api/middleware.go:51-53). Affected All released versions up to v0.3.0. Threat model Read access to nebula-mgmt.db: backup, snapshot, file-system access, future SQL-injection sink. The principle of defense-in-depth: API keys are hashed at rest; enrollment tokens — which grant the same lifecycle authority over a host's identity — are not. An attacker who reads the DB before a legitimate agent enrolls can consume the single-use token first, mint a cert against their own keypair, and take the agent's intended Nebula identity. Suggested fix 1. Schema migration: rename enrollmenttokens.token → tokenhash (or add the new column and drop the old after backfill of pending rows). 2. Store SHA-256 of token on create: 3. ConsumeToken accepts the raw…

Published by the source

22 Jun 2026, 22:57 UTC

Last modified by the source

22 Jun 2026, 22:57 UTC

Source last checked

26 Oct 2026, 15:24 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-ghmh-jhmj-wcmf

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: GHSA-ghmh-jhmj-wcmf

Advisory: nebula-mesh's stores enrollment tokens unhashed in SQLite
IDs: GHSA-ghmh-jhmj-wcmf
Record: https://patchnext.com/advisories/ghsa-ghmh-jhmj-wcmf (revision 1, source checked 26 Oct 2026, 15:24 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.0)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/juev/nebula-mesh 0.3.2. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/juev/nebula-mesh: affected <= 0.3.1; fixed in 0.3.2

## Suggested inspection (read-only)
- Go github.com/juev/nebula-mesh: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/juev/nebula-mesh.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-ghmh-jhmj-wcmf (GitHub-reviewed advisory GHSA-ghmh-jhmj-wcmf lists affected ranges: Go github.com/juev/nebula-mesh >=0 <=0.3.1)

Commands are suggestions: review each one before running it.