Connect your agent
AdvisoriesCriticalCheck your lockfilePluginHow it worksPricing Connect your agent

Advisory record · GHSA-m3cx-mwpg-32jg

nebula-mesh: Unauthenticated OIDC login endpoint allocates unbounded in-memory state entries without rate limiting

CVSS 5.3 MediumEPSS 0.0060 · 49th percentile

Published by the GitHub Advisory Database at 14 Jul 2026, 20:19 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
github.com/forgekeep/nebula-meshGo>=0.2.0, <0.5.00.5.0
Identifiers
GHSA-m3cx-mwpg-32jg · CVE-2026-55512 · GO-2026-5989
Weakness (CWE)
CWE-400
Tags
Published
14 Jul 2026
Updated
23 Jul 2026

Machine-written summary

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

Versions 0.2.0 up to but not including 0.5.0 of the Go module github.com/forgekeep/nebula-mesh are affected. When OIDC is enabled, the unauthenticated /ui/oidc/login endpoint stores a new in-memory state entry on every request, and these entries are not rate-limited or capped in number. A remote attacker with network access can repeatedly send requests to grow server memory for the ten-minute state lifetime, which risks availability degradation. Upgrade to version 0.5.0. The source does not list a 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
5.3 Medium 3.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0060, the 49th percentile, on 15 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:57 UTC First seen by agentprime
  2. 31 Oct 2026, 14:57 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.