dbcve.org
NetmakerApplication · Gravitl

CVE-2026-29194

HIGH · 8.1 CVSS v3.1 Published 2026-03-07
Fix available
A fix is available. Upgrade to 1.5.0 or later.
See remediation →
87/100
Remediation priority · High
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Netmaker makes networks with WireGuard. Prior to version 1.5.0, the Authorize middleware in Netmaker incorrectly validates host JWT tokens. When a route permits host authentication (hostAllowed=true), a valid host token bypasses all subsequent authorization checks without verifying that the host is authorized to access the specific requested resource. Any entity possessing knowledge of object identifiers (node IDs, host IDs) can craft a request with an arbitrary valid host token to access, modify, or delete resources belonging to other hosts. Affected endpoints include node info retrieval, host deletion, MQTT signal transmission, fallback host updates, and failover operations. This issue has been patched in version 1.5.0.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Authorize middleware in Netmaker versions prior to 1.5.0 incorrectly validates host JWT tokens. When routes permit host authentication (hostAllowed=true), a valid host token bypasses all subsequent authorization checks without verifying the host is authorized to access the specific requested resource, allowing attackers with knowledge of object identifiers to access, modify, or delete resources belonging to other hosts.

MitigationUpgrade to Netmaker version 1.5.0 or later to apply the patch that fixes the authorization bypass in the Authorize middleware.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
NetmakerApplication
Affected:< 1.5.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Netmaker version
    Run 'docker images' or check docker-compose.yml for the netmaker image tag, or run the netmaker binary with version flag (e.g., './netmaker --version')
    Affected if The version is below 1.5.0 or the image tag shows a version prior to v1.5.0
  2. Locate route configurations that enable host authentication
    Search Netmaker configuration files or YAML definitions for 'hostAllowed: true' settings in route or API endpoint definitions
    Affected if Routes or endpoints are configured with hostAllowed=true, indicating host-based authentication is permitted for those resources
  3. Examine the Authorize middleware implementation
    Review the middleware code or configuration that handles the authorization logic for host tokens, looking for any code that validates host authorization against the requested resource object ID
    Affected if The middleware grants access based solely on a valid host token without verifying the host is authorized for the specific resource being accessed (e.g., missing resource ownership validation)
  4. Check API endpoint definitions for host-accessible routes
    Review Netmaker API route definitions or swagger/openapi specifications to identify which endpoints permit host token authentication and what object identifiers they accept
    Affected if Endpoints accept object identifiers (such as host IDs, network IDs, or other resource IDs) as parameters and permit access with only a valid host token

You are affected if Netmaker version is below 1.5.0 and routes exist with hostAllowed=true where the Authorize middleware does not verify that the host token holder owns or is authorized for the specific resource being requested.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.5.0 or later
Fixed in 1.5.0
Interim mitigation

Upgrade to Netmaker version 1.5.0 or later to apply the patch that fixes the authorization bypass in the Authorize middleware.

Recommended fix High confidence

1.5.0

  1. Back up your current Netmaker configuration and data directory
  2. Stop the Netmaker services
  3. Upgrade Netmaker to version 1.5.0 using your deployment method (e.g., docker pull, helm upgrade, or binary replacement)
  4. Verify the upgrade completed successfully by checking the version
  5. Restart Netmaker services
  6. Test that the authorization middleware correctly validates host tokens for the affected endpoints (node info retrieval, host deletion, MQTT signal, fallback host updates, failover operations)

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Netmaker Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing4.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,540
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,464.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-29194 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-29194 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data