dbcve.org
NetmakerApplication

CVE-2026-29771

MEDIUM · 6.5 CVSS v3.1 Published 2026-03-07
Fix available
A fix is available. Upgrade to 1.2.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.2.0, the /api/server/shutdown endpoint allows termination of the Netmaker server process via syscall.SIGINT. This allows any user to repeatedly shut down the server, causing cyclic denial of service with approximately 3-second restart intervals. This issue has been patched in version 1.2.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 /api/server/shutdown endpoint in Netmaker prior to 1.2.0 lacks proper authentication, allowing any user to send a SIGINT signal that terminates the server process. This creates a cyclic denial of service as the server automatically restarts approximately every 3 seconds, repeatedly being shut down.

MitigationUpgrade to Netmaker version 1.2.0 or later which patches this vulnerability. If immediate upgrade is not possible, implement network-level access controls to restrict access to the /api/server/shutdown endpoint.

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.2.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
None
Availability
High

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

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 Netmaker installation method
    Determine how Netmaker is deployed (docker container, binary, or managed service). For docker, run 'docker ps' and look for netmaker containers. For binaries, check running processes.
    Affected if Netmaker is running as a container or binary but version cannot be determined or is below 1.2.0
  2. Check installed Netmaker version
    For docker deployments, run 'docker images' or inspect the container labels. For binary deployments, check the binary version via '--version' flag or API call to /api/version. Compare against the affected range: versions prior to 1.2.0 are vulnerable.
    Affected if Netmaker version is below 1.2.0
  3. Verify network exposure of the shutdown endpoint
    Test if the /api/server/shutdown endpoint is reachable from untrusted networks. This can be done via curl or similar: curl -X POST http://<netmaker-host>/api/server/shutdown. Check if the server has proper network segmentation or firewall rules.
    Affected if The /api/server/shutdown endpoint is accessible from network segments that contain untrusted users or from the public internet
  4. Check API authentication configuration
    Review Netmaker's server configuration for authentication settings. The endpoint should require valid authentication tokens or API keys. Check if unauthenticated requests to /api/server/shutdown are rejected.
    Affected if The /api/server/shutdown endpoint accepts requests without authentication (no token, API key, or valid credentials required)

A Netmaker server is affected if it is running version 1.2.0 or earlier AND the /api/server/shutdown endpoint is accessible without authentication from an untrusted network.

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.2.0 or later
Fixed in 1.2.0
Interim mitigation

Upgrade to Netmaker version 1.2.0 or later which patches this vulnerability. If immediate upgrade is not possible, implement network-level access controls to restrict access to the /api/server/shutdown endpoint.

Recommended fix High confidence

Netmaker v1.2.0 or later

  1. 1. Back up your Netmaker configuration and data before upgrading.
  2. 2. Upgrade Netmaker to version 1.2.0 or later. For Docker deployments, update the image tag in your docker-compose.yml or run `docker-compose pull` followed by `docker-compose up -d`. For binary installations, download the new binary from the releases page.
  3. 3. After upgrading, verify the server starts successfully and is accessible.
  4. 4. Confirm that the /api/server/shutdown endpoint is now properly protected and requires appropriate authentication/authorization.

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

Fix this in Netmaker Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
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,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-29771 — 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-29771 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