Advisory record · GHSA-ghmh-jhmj-wcmf

nebula-mesh's stores enrollment tokens unhashed in SQLite

CVSS 4.0, no score published

Published by the GitHub Advisory Database at 22 Jun 2026, 22:57 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
github.com/juev/nebula-meshGo<0.3.20.3.2
Identifiers
GHSA-ghmh-jhmj-wcmf · GO-2026-5399
Weakness (CWE)
CWE-312
Published
22 Jun 2026
Updated
25 Jun 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

GHSA-ghmh-jhmj-wcmf affects nebula-mesh versions below 0.3.2. Enrollment tokens are stored unhashed in the SQLite database. An attacker who can read that database before a legitimate agent enrolls could consume the token first and take the agent's intended Nebula identity. Upgrade to version 0.3.2. The source gives no other workaround.

Written 6 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
Not published None 4.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 GitHub Advisory Database
  • CISA KEV Not listed.
  • EPSS No score.

Timeline

  1. 31 Oct 2026, 15:06 UTC First seen by agentprime
  2. 31 Oct 2026, 15:06 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.