Summary
Netmaker has a boolean‑based SQL Injection
SQL Injection in Netmaker SQLite Database Backend
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.
// 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 parameter to manipulate the query logic.
Because this injection is boolean-based, attackers extract data indirectly by observing the outcome of the operation:
If the injected condition evaluates true, the DNS record is deleted.
If the condition evaluates false, the DNS record remains.
By repeating this process, an attacker can infer information such as:
Database table names
Column names
Column values
Value lengths
Impact
An authenticated attacker can exploit this vulnerability to extract data from arbitrary database tables when using the SQLite backend.
Unaffected backend:
PostgreSQL (uses parameterised queries with $1, $2 placeholders)
Patches
This vulnerability is fixed in version (fill in).
The patch replaces string concatenation with parameterised SQL queries for all user-supplied values in database operations.
---
Credit
Artem Danilov
(Positive Technologies)
Daniil Satyaev (Independent)
Impact
Untrusted input alters a database query, allowing the attacker to read or modify data the query was not intended to access. Typical impact: data disclosure or modification.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is CVE-2026-32599? CVE-2026-32599 is a medium-severity SQL injection vulnerability in github.com/gravitl/netmaker (go), affecting versions < 1.5.0. It is fixed in 1.5.0. Untrusted input alters a database query, allowing the attacker to read or modify data the query was not intended to access.
- Which versions of github.com/gravitl/netmaker are affected by CVE-2026-32599? github.com/gravitl/netmaker (go) versions < 1.5.0 is affected.
- Is there a fix for CVE-2026-32599? Yes. CVE-2026-32599 is fixed in 1.5.0. Upgrade to this version or later.
- Is CVE-2026-32599 exploitable, and should I be worried? Whether CVE-2026-32599 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2026-32599 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2026-32599? Upgrade
github.com/gravitl/netmakerto 1.5.0 or later.