How broadly exploitable is this vulnerability?

Exploitability depends on whether an attacker can influence the metric or identifier names that Glances passes to the DuckDB exporter. In environments where metric definitions or labels are tightly controlled and not user-influenced, the practical risk is lower; where untrusted sources can shape those names, the risk is significantly higher.

Does an attacker need direct access to DuckDB to exploit this?

No direct database access is required. Exploitation occurs through the Glances process itself: the attacker only needs a way to control the values that Glances uses when constructing SQL identifiers, which then get executed by the embedded DuckDB engine.

What is the safest general fix pattern?

Replace all f-string or concatenation-based SQL that includes variable identifiers with a safe construction approach, such as composable SQL objects or dedicated identifier-escaping utilities, and enforce strict validation of any identifier sources. Parameterization should remain in place for values, but identifier handling must be hardened as well.

Severity:

HIGH RISK

(7.0)

SQL Injection via Unsanitized Identifiers (CWE-89) in Glances DuckDB Export Module

CVE-2026-32611

Published:

Mar 18, 2026

Status:

Analyzed

Summary

Affected Context

Exploit Preconditions

Why This Happens

Potential Impact

General Mitigation Guidance

How Teams Detect Issues Like This

Frequently Asked Questions

Source

NDV

Recent Vulnerabilities

CWE-918

HIGH RISK

HIGH

(8.6)

Server-Side Request Forgery (CWE-918) in OpenClaw Zalo Plugin sendPhoto

Unauthorized Access to Internal Resources via SSRF

May 6, 2026

CWE-863

HIGH RISK

HIGH

(8.8)

Authorization Bypass (CWE-863) in OpenClaw Matrix Room Control Commands

Privilege Escalation via Bypassed Access Control

May 6, 2026

Vulnerability Type

Category:

SQL Injection

CWE:

CWE-89

Impact:

Arbitrary SQL Execution in Embedded DuckDB Database

Severity:

HIGH RISK

(7.0)

CVSS Version:

3.1

Vulnerability Type

Category:

SQL Injection

CWE:

CWE-89

Impact:

Arbitrary SQL Execution in Embedded DuckDB Database

Severity:

HIGH RISK

(7.0)

CVSS Version:

3.1

Catch This CVE While Code Is Being Written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Get Started

Ship clean & secure code faster

Start Free Trial

Get Pentest Report

Ship clean & secure code faster

Start Free Trial

Get Pentest Report

Ship clean & secure code faster

Start Free Trial

Get Pentest Report

CodeAnt AI is an offensive and defensive security platform.

Defensive + offensive security.

From first line of code to a pentest
that knows every line of it.

SOC 2 Type II certified | CodeAnt AI is independently audited and compliant with SOC 2 Type II security standards

Ask AI for summary of CodeAnt

Defensive + offensive security.

From first line of code to a pentest
that knows every line of it.

Ask AI for summary of CodeAnt

Defensive + offensive security.

From first line of code to a pentest
that knows every line of it.

Ask AI for summary of CodeAnt

SQL Injection via Unsanitized Identifiers (CWE-89) in Glances DuckDB Export Module

Summary

Affected Context

Exploit Preconditions

Why This Happens

Potential Impact

General Mitigation Guidance

How Teams Detect Issues Like This

Frequently Asked Questions

Source

Recent Vulnerabilities

HIGH RISK

HIGH

(8.6)

Server-Side Request Forgery (CWE-918) in OpenClaw Zalo Plugin sendPhoto

HIGH RISK

HIGH

(8.8)

Authorization Bypass (CWE-863) in OpenClaw Matrix Room Control Commands

Vulnerability Type

Vulnerability Type

Vulnerability Type

Catch This CVE While Code Is Being Written

Ship clean & secure code faster

Ship clean & secure code faster

Ship clean & secure code faster

Product

Compare

Company

Developers

Legal

Product

Compare

Company

Developers

Legal

Product

Compare

Company

Developers

Legal