Categories
CVE-2026-32599

SQL Injection in github.com/gravitl/netmaker (CVE-2026-32599)

Summary

SQL injection in github.com/gravitl/netmaker (CVE-2026-32599). Risk of unauthorized operations or information disclosure. Exploitable via DELETE /api/dns/{network}/{domain}. Mitigation: upgrade to 1.5.0 or later.

Original description

The description as published by the source.

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 explo…

Source: NIST National Vulnerability Database NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-32599 has been found in github.com/gravitl/netmaker.
Attackers can target a specific entry point like DELETE /api/dns/{network}/{domain} over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade github.com/gravitl/netmaker to 1.5.0 or later.
If unsure, ask your IT team or search "github.com/gravitl/netmaker CVE-2026-32599" on the vendor's site.

CVE-2026-32599 (github.com/gravitl/netmaker) — CWE-89
Attack surface: DELETE /api/dns/{network}/{domain} / sqliteDeleteRecord / DELETE
Patched: 1.5.0 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

SQL injection (CWE-89) exists in github.com/gravitl/netmaker. Attackers reach the vulnerable code path via DELETE /api/dns/{network}/{domain}.

📍 Affected scope

Check the vendor advisory for the affected versions of github.com/gravitl/netmaker. Attack surface: DELETE /api/dns/{network}/{domain} / sqliteDeleteRecord / DELETE.

🔥 Severity

Severity: ?. Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 1.5.0.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual DELETE /api/dns/{network}/{domain} requests with malformed payloads or SQL meta-characters. Run grep -r 'github.com/gravitl/netmaker' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify
    grep -r 'github.com/gravitl/netmaker' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で github.com/gravitl/netmaker を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Hunt for indicators of compromise detect
    grep 'DELETE /api/dns/{network}/{domain}' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'

    アクセスログで DELETE /api/dns/{network}/{domain} への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。

  3. 3
    Apply patch patch
    Upgrade github.com/gravitl/netmaker to 1.5.0

    ステージング環境で 1.5.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。

  4. 4
    Post-deployment verification verify
    Replay attack against DELETE /api/dns/{network}/{domain} on staging to confirm patch closes the vector

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。

Affected packages

go github.com/gravitl/netmaker
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.5.0"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details