Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🐹 Go
Not in CISA KEV

Netmaker has a boolean‑based SQL InjectionGHSA-r8cr-4f9w-7r75

GHSA-r8cr-4f9w-7r75 is a SQL Injection vulnerability in github.com/gravitl/netmaker. A fix is available for github.com/gravitl/netmaker — see the affected versions and patch details below.

Also known asCVE-2026-32599GO-2026-6485
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Oct 29, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

  • CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-r8cr-4f9w-7r75.

EPSS Exploitation Probability

via FIRST.org ↗
0.4%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs29th percentile — riskier than 29% of all scored CVEsHighest risk
0.00%0.29%0.57%0.86%0.4%0.4%Oct 26Oct 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected
🐹github.com/gravitl/netmaker

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

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.

// 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)

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
🐹Gogithub.com/gravitl/netmakerall versions1.5.0go get github.com/gravitl/netmaker@v1.5.0

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/gravitl/netmaker, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update github.com/gravitl/netmaker to 1.5.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-r8cr-4f9w-7r75 is resolved across your whole dependency graph.

  3. Workarounds

    Until you can upgrade, make sure every query built from user input uses parameterised statements or a prepared-statement API rather than string concatenation, and reduce the database account's privileges so an injected query cannot read or alter data beyond what the feature needs.

Frequently Asked Questions

# 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 databa
O3 Security · Impact-Aware SCA

Is GHSA-r8cr-4f9w-7r75 in your dependencies?

Find it across Go, including transitive dependencies.

Netmaker has a boolean‑based SQL Injection