CVE-2026-38651: Gravitl Netmaker authentication bypass in VerifyHostToken

CVE-2026-38651 · Severity: high · CVSS 8.2 · Published 2026-04-28

Netmaker, a platform for managing virtual overlay networks, contains a security flaw that allows unauthorized users to bypass authentication. By creating a specially crafted security token, an attacker can impersonate any device on the network. This could lead to the theft of sensitive configuration data, including encrypted passwords and network keys, potentially compromising the entire virtual network.

Technologies: github.com/gravitl/netmaker (Go), Netmaker. Vendors: Go, Netmaker.

Quick answers

Is CVE-2026-38651 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-38651 being exploited in the wild.
How severe is CVE-2026-38651?
High severity, with a CVSS score of 8.2, published 28 April 2026.
Which products and versions are affected?
github.com/gravitl/netmaker (Go) SEMVER:introduced=0,fixed=1.5.0.
Is there a fix for CVE-2026-38651?
Yes. github.com/gravitl/netmaker (Go): upgrade to 1.5.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-38651 attacked?
It is attacked over the network, in an operating system.
Am I affected by CVE-2026-38651?
Check whether you run github.com/gravitl/netmaker (Go) or Netmaker 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/gravitl/netmaker (Go): upgrade to 1.5.0 or later
    go get github.com/gravitl/netmaker@v1.5.0

Technical details

An authentication bypass exists in Netmaker's 'VerifyHostToken' function within 'logic/jwts.go'. The implementation uses the 'golang-jwt/jwt' library but fails to check the 'token.Valid' field or the returned error after calling 'ParseWithClaims'; it only verifies that the token object itself is non-nil. Consequently, any structurally valid JWT signed with an arbitrary key is accepted. An unauthenticated remote attacker can exploit this to impersonate any host ID and access sensitive endpoints such as '/api/v1/host', which returns bcrypt-hashed passwords, MQTT credentials, and WireGuard peer data. The issue is resolved in version 1.5.0 by properly validating the token state.

Affected products

  • Gravitl Netmaker < 1.5.0

Identifiers

  • CVE-2026-38651
  • GHSA-qpv2-rwc8-c993
  • GO-2026-5588

Timeline

  • 2026-01-22: disclosed: Vulnerability reported to vendor
  • 2026-02-24: patched: Fixed in commit 5309aa70
  • 2026-04-28: advisory: CVE published

References

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