Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Medium, CVSS 5.3amended

Netmaker has a boolean‑based SQL Injection

CVE-2026-32599GHSA-r8cr-4f9w-7r75

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (github.com/gravitl/netmaker 1.5.0), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
5.3 · CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N · score source
EPSS
  • CVE-2026-32599: 0.36% estimated exploitation activity in the next 30 days; percentile 29.59 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

SQL Injection in Netmaker SQLite Database Backend Summary The sqliteDeleteRecord function in Netmaker's database layer constructs SQL DELETE statements using direct string concatenation of user-supplied input. This allows an authenticated attacker to perform boolean-based SQL injection. --- Details The endpoint: DELETE /api/dns/{network}/{domain} passes user-controlled path parameters through the following flow: logic.DeleteDNS → database.DeleteRecord → sqliteDeleteRecord Depending on the configured database backend, the request eventually reaches the SQLite database implementation. Vulnerable Code The SQL query is constructed using direct string concatenation without parameterization. go // database/sqlite.go deleteSQL := "DELETE FROM " + tableName + " WHERE key = \"" + key + "\"" The key value originates from user input ({domain} path parameter) and is embedded directly into the SQL query. Exploitation An authenticated attacker can inject SQL operators into the {domain} path…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 4 · amended ·

    Amended from ghsa record GHSA-r8cr-4f9w-7r75

  2. Revision 3 · amended ·

    Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

  3. Revision 2 · amended ·

    Amended from osv record GO-2026-6485

  4. Revision 1 · created ·

    Published from osv record GHSA-r8cr-4f9w-7r75

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-32599

Advisory: Netmaker has a boolean‑based SQL Injection
IDs: CVE-2026-32599, GHSA-r8cr-4f9w-7r75
Record: https://patchnext.com/advisories/cve-2026-32599 (revision 4, source checked 26 Oct 2026, 15:29 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/gravitl/netmaker 1.5.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/gravitl/netmaker: affected < 1.5.0; fixed in 1.5.0

## Suggested inspection (read-only)
- Go github.com/gravitl/netmaker: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/gravitl/netmaker.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-r8cr-4f9w-7r75 (OSV record GHSA-r8cr-4f9w-7r75 lists affected ranges: Go github.com/gravitl/netmaker >=0 <1.5.0 (fixed))
- Verified: https://osv.dev/vulnerability/GO-2026-6485 (OSV record GO-2026-6485 lists affected ranges: Go github.com/gravitl/netmaker >=0 <1.5.0 (fixed))
- Verified: https://github.com/advisories/GHSA-r8cr-4f9w-7r75 (GitHub-reviewed advisory GHSA-r8cr-4f9w-7r75 lists affected ranges: Go github.com/gravitl/netmaker >=0 <1.5.0)

Commands are suggestions: review each one before running it.

Loading voting…