CVE-2026-38651

Netmaker authentication bypass

8.2 HIGHPublic exploitEPSS 0.44%

Published28 Apr 2026

Description

Authentication Bypass vulnerability exists in Netmaker versions prior to 1.5.0. The VerifyHostToken function in logic/jwts.go fails to validate the JWT signature when verifying host tokens. An attacker can forge a JWT signed with any arbitrary key and use it to impersonate any host in the network, gaining access to sensitive information

CVSS 3.1 breakdown

Attack vectorNetwork

Attack complexityLow

Privileges requiredNone

User interactionNone

ScopeUnchanged

ConfidentialityHigh

IntegrityLow

AvailabilityNone

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N

Affected products

Netmaker< 1.5.0

Remediation

Fixed in

Netmaker≥ 1.5.0

Patch & vendor advisories

https://github.com/gravitl/netmaker/commit/5309aa70d464ef565911369714d661a61481a79b

References

https://github.com/gravitl/netmaker/commit/5309aa70d464ef565911369714d661a61481a79bPatch
https://www.zyenra.com/advisories/netmaker-jwt-verification-bypassExploitThird Party Advisory
https://www.zyenra.com/advisories/netmaker-jwt-verification-bypass/ExploitThird Party Advisory
https://www.zyenra.com/blog/netmaker-jwt-verification-bypassExploitThird Party Advisory

Related CVEs

Recent high-severity vulnerabilities sharing a weakness type.

Frequently asked

Is CVE-2026-38651 being actively exploited?

CVE-2026-38651 is not in the CISA KEV catalog. A public exploit reference exists, so treat it as exploitable. Its EPSS exploit probability is 0.44%.

How severe is CVE-2026-38651?

CVE-2026-38651 has a CVSS 3.1 base score of 8.2, rated high. EPSS estimates a 0.44% probability of exploitation.

Which products are affected by CVE-2026-38651?

Affected products include Netmaker.

How do I fix CVE-2026-38651?

Upgrade affected software to a fixed version, for example Netmaker 1.5.0 or later, then confirm no affected versions remain in your inventory.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2026-38651 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

See how prioritisation works Book a demo

Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.