NetmakerApplication · Gravitl

CVE-2026-29195

MEDIUM · 6.5 CVSS v3.1 Published 2026-03-07
Fix available
A fix is available. Upgrade to 1.5.0 or later.
See remediation →
71/100
Remediation priority · Elevated
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 user update handler (PUT /api/users/{username}) lacks validation to prevent an admin-role user from assigning the super-admin role during account updates. While the code correctly blocks an admin from assigning the admin role to another user, it does not include an equivalent check for the super-admin role. 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 PUT /api/users/{username} endpoint in Netmaker prior to version 1.5.0 lacks authorization checks to prevent admin-role users from assigning the super-admin role to any user, including themselves. While the code correctly blocks admins from granting the admin role to others, it omits the equivalent validation for the super-admin role, allowing privilege escalation.

MitigationUpgrade to Netmaker version 1.5.0 or later, which adds the missing validation to prevent admin-role users from assigning the super-admin role.

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
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/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. Check installed Netmaker version
    Query the Netmaker API version endpoint or check the running container/binary version. On Linux systems, you can also check: docker images | grep netmaker or the systemd service version.
    Affected if The version is lower than 1.5.0 (e.g., 1.4.x, 1.3.x, etc.)
  2. Identify admin-role users
    Query the user database or API endpoint GET /api/users and review the role field for each user account. Look for users with the 'admin' role.
    Affected if Any user accounts exist with the admin role in the system
  3. Check for unexpected super-admin users
    Query GET /api/users and examine users with the 'super-admin' or 'superadmin' role. Compare this list against known legitimate super-admin accounts documented in your organization.
    Affected if A user has super-admin role that was not explicitly created as super-admin, indicating possible privilege escalation
  4. Review API access logs for the user endpoint
    Inspect Netmaker server logs or API access logs for PUT /api/users/{username} requests that modified the role field, particularly where role was set to super-admin.
    Affected if Logs show PUT requests to /api/users endpoint modifying roles to super-admin, especially by users who previously only had admin role

You are affected if Netmaker version is below 1.5.0 AND admin-role users exist who could potentially escalate their privileges through the unvalidated PUT /api/users endpoint.

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, which adds the missing validation to prevent admin-role users from assigning the super-admin role.

Recommended fix High confidence

1.5.0

  1. Upgrade Netmaker to version 1.5.0 or later

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

Fix this in Netmaker Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

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-29195 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