Vulnerability in github.com/gravitl/netmaker (CVE-2026-38651)
Summary
Vulnerability in github.com/gravitl/netmaker (CVE-2026-38651). Confidential information can be exposed externally. Exploitable via VerifyHostToken. Mitigation: upgrade to 1.5.0 or later.
Original description
The description as published by the source.
Netmaker by Gravitl is an open-source WireGuard-based networking platform for creating and managing virtual overlay networks. The VerifyHostToken function in logic/jwts.go does not validate the JWT signature when verifying host tokens. After calling jwt.ParseWithClaims, the function only checks whether the returned token object is non-nil. It does not check token.Valid or the returned error. An attacker can forge a JWT signed with any key, set the claims to any host ID, and pull that host's full configuration including bcrypt-hashed passwords, MQTT credentials, and WireGuard peer data. The issue was patched in v1.5.0.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-38651 has been found in github.com/gravitl/netmaker.
Attackers can target a specific entry point like VerifyHostToken over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 8.2/10.
What to do: upgrade github.com/gravitl/netmaker to 1.5.0 or later.
If unsure, ask your IT team or search "github.com/gravitl/netmaker CVE-2026-38651" on the vendor's site.
CVE-2026-38651 (github.com/gravitl/netmaker) — CWE-347 / CVSS v3 8.2
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: VerifyHostToken / jwt.ParseWithClaims / token.Valid
Patched: 1.5.0 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-347) exists in github.com/gravitl/netmaker. Attackers reach the vulnerable code path via VerifyHostToken without authentication.
Check the vendor advisory for the affected versions of github.com/gravitl/netmaker. Attack surface: VerifyHostToken / jwt.ParseWithClaims / token.Valid.
Severity: High (CVSS 8.2/10). Confidential information can be exposed externally.
Update to 1.5.0.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'github.com/gravitl/netmaker' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'github.com/gravitl/netmaker' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
github.com/gravitl/netmakerを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade github.com/gravitl/netmaker to 1.5.0ステージング環境で 1.5.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- exploit zyenra.com
- exploit zyenra.com
- package github.com
- web github.com
- web zyenra.com