Skip to main content

SigNoz CVE-2026-93292

| EUVDEUVD-2026-82315 HIGH
SQL Injection (CWE-89)
2026-09-17 VulnCheck
8.4
CVSS 4.0 · Vendor: VulnCheck
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Authenticate to SigNoz with low-priv account
  2. Delivery
    Define trace-funnel step with crafted service_name/span_name
  3. Exploit
    Payload breaks out of ClickHouse string literal
  4. Execution
    Injected SQL executes in backend
  5. Impact
    Read query results from HTTP response

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Parameterized queries, prepared statements
MITRE ATT&CK

2 techniques across 2 tactics: Initial Access, Persistence

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Requires an authenticated SigNoz account (PR:L) with access to the trace-funnel analytics feature, which exists only in versions 0.88.0 through 0.142.0. The concrete injection points are the service_name and span_name fields within funnel step definitions, which are interpolated into ClickHouse string literals without escaping. No user interaction is needed and the endpoint is network-reachable. The primary limiting factor is the authentication requirement - an attacker must already possess valid credentials (or exploit them via a compromised/insider/multi-tenant account); default-configuration unauthenticated exploitation is not possible.

Impact

Real, actionable risk. The CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:L/UI:N, VC:H/SC:H, score 8.4 High) describes a network-reachable, low-complexity SQL injection requiring only a low-privileged authenticated account and no user interaction - a class of flaw that is reliably weaponizable once a working request is known. The SC:H (subsequent-system confidentiality High) correctly reflects that injection lands in the backing ClickHouse datastore, a separate system, so a successful attack reads data well beyond the SigNoz app's own scope. No EPSS score, KEV listing, or POC was provided in the intelligence, so exploitation is 'no public exploit identified at time of analysis' - this is NOT active exploitation and should not be treated as such. The main mitigating factor is the PR:L authentication gate: the attacker must first hold a valid SigNoz account, which limits opportunistic mass exploitation but does nothing against insiders, compromised credentials, or multi-tenant deployments. VC:H with only VI:L/VA:L is consistent with the description ('read results in HTTP responses'), i.e. this is primarily a data-disclosure primitive rather than a destructive one. No signals conflict; the network vector, low complexity, and authenticated requirement are all internally consistent with the described attack.

Exploit ScenarioDerived

An attacker with any authenticated SigNoz account opens the trace-funnel analytics feature and defines a funnel step whose service_name or span_name field contains a crafted single-quote-breaking SQL payload. Because those fields are interpolated directly into ClickHouse string literals without escaping, the injected SQL executes against the telemetry database and the query results are returned in the HTTP response, letting the attacker read arbitrary data. No public exploit code was identified in the provided intelligence, but the vulnerable code paths are pinpointed in the vendor advisory (clickhouse_queries.go and http_handler.go).

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
Patch available 0.3% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Sep 17, 2026

SQL injection in SigNoz's trace-funnel analytics endpoints lets an authenticated user break out of the ClickHouse string literals built from the service_name and span_name fields of funnel step definitions and read the results of arbitrary queries back in the HTTP response. All self-hosted deployments from 0.88.0 up to (but not including) 0.142.1 are affected; exploitation requires a valid SigNoz account with access to the trace-funnel feature, is network-reachable, and needs no user interaction, and no public exploit code was identified at time of analysis. The assessed impact is high confidentiality loss that extends to the underlying ClickHouse store (scope change) with limited integrity impact, which is why the issue carries a high-severity score despite the authentication prerequisite.

RemediationAI

Vendor-released patch: upgrade to SigNoz 0.142.1 or later (release tag v0.142.1, https://github.com/SigNoz/signoz/releases/tag/v0.142.1), which the vendor advisory GHSA-w5pf-xwjh-vr5v pairs with the remediation commits 8e00c0405697659bd4994a5de446cf3028c0f76d and 8286e787b296b291a26a14d20407a335fcfbac25 that add pkg/clickhousesql with proper literal and identifier quoting. If an immediate upgrade is not possible, reduce exposure by restricting access to the trace-funnel analytics feature to trusted accounts only via authentication/role configuration, since the flaw requires a valid low-privilege account and cannot be reached unauthenticated, at the cost of disabling a legitimate feature for general users. Constrain the ClickHouse credentials used by the SigNoz query service to read-only on the signoz database and deny access to the system and information_schema databases and to file-reading table functions, following the validation model the patch implements, accepting that some legitimate administrative queries may stop working. Additionally, network-segment ClickHouse so that only the SigNoz query service can reach its native protocol port, and review existing funnel step definitions for quote, backslash or SQL keyword content that may indicate prior probing, since successful exploitation may already have leaked telemetry data.

Affected VersionsENISA

signoz 0.88.0 <0.142.1

Affected Packages

euvd signoz fix: 0.142.1

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

SigNoz stores telemetry in ClickHouse and generates analytics SQL as text, largely through the go-sqlbuilder library executed with clickhouse-go. In the trace-funnel module (pkg/modules/tracefunnel/clickhouse_queries.go) and the associated HTTP handler (pkg/query-service/app/http_handler.go), the user-supplied service_name and span_name values from funnel step definitions were concatenated directly into ClickHouse string literals rather than being quoted or bound as parameters, which is the classic CWE-89 root cause: special elements (quotes and backslash escapes) in attacker-controlled input are not neutralized before the string is interpreted as SQL. Because the injected text is executed against the analytics store, the vulnerability crosses a trust boundary between the SigNoz application and ClickHouse, giving scope change and read access to data beyond the application's own authorization model, which is why the results can be exfiltrated through normal HTTP responses to the analytics endpoint. The upstream fix commits 8e00c0405697659bd4994a5de446cf3028c0f76d and 8286e787b296b291a26a14d20407a335fcfbac25 introduce a dedicated pkg/clickhousesql package providing StringLiteral, Identifier, Literal and LikePattern helpers, require sqlbuilder.Escape to be applied once to any compiled builder text, add documentation (docs/contributing/go/clickhousesql.md) covering the interaction between go-sqlbuilder placeholder resolution ($0, ${name}) and clickhouse-go argument binding, and add a validator (ErrIfStatementIsNotValid) that only permits a single SELECT when users type queries into the ClickHouse query panel.

Know when Signoz gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (VulnCheck) PRIMARY 8.4 HIGH
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:L/VA:N/SC:H/SI:L/SA:N
vuln.today AI 8.5 HIGH

Network-reachable authenticated (PR:L) injection into a separate ClickHouse backend (S:C); primary impact is data read (C:H) with limited write capability (I:L) and no availability effect.

3.1 AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:L/A:N
4.0 AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:L/VA:N/SC:H/SI:L/SA:N

Primary rating from Vendor (VulnCheck).

CVSS VectorVendor: VulnCheck

Attack Vector
Network
Attack Complexity
Low
Attack Requirements
None
Privileges Required
Low
User Interaction
None
Vulnerable system: Confidentiality
High
Vulnerable system: Integrity
Low
Vulnerable system: Availability
None
Subsequent system: Confidentiality
High
Subsequent system: Integrity
Low
Subsequent system: Availability
None

DescriptionCVE.org

SigNoz versions from 0.88.0 before 0.142.1 contain a SQL injection vulnerability in trace-funnel analytics endpoints that interpolate service_name and span_name fields into ClickHouse string literals without escaping. Authenticated attackers can inject SQL through funnel step definitions to execute arbitrary queries and read results in HTTP responses.

Technical POC Analysis

CWE-89 (Improper Neutralization of Special Elements used in an SQL Command).

Full technical POC analysis - root cause, step-by-step exploitation and patch breakdown - is part of the Pro and Business plans.

Executive ViewAI

Why It Matters

A high-severity SQL injection flaw in SigNoz's trace-funnel analytics endpoints (CVE-2026-93292, CVSS 8.4) affects every self-hosted deployment from version 0.88.0 up to but not including 0.142.1, allowing a user with a valid SigNoz account and access to the trace-funnel feature to read data far beyond their intended scope - including records in the underlying ClickHouse store that back the platform. Because SigNoz often holds sensitive telemetry and operational metadata, unauthorized read access at that layer can expose system internals and supporting data that leadership is accountable for protecting. The exposure is limited to organizations running the affected self-hosted versions, and no public exploit code was identified at time of analysis.

Business Impact: High
Compensating Controls

Apply vendor patch.

Threat Intelligence Overview

EPSS Score
0.3%
Top 77% exploitable
Prevalence
Medium
popular open-source observability/APM platform, self-hosted, not universally deployed
Social Media
1
Sightings
Data Quality
6 sources
Confidence: High

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.3%
Patch available Yes
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
Poc
System Exposure· derived
Open
Automatable
No
Human Impact
High
Technical Impact
Partial

Priority Score

42
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +42
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

SQL injection exploits the way applications construct database queries by mixing user input directly into SQL statements.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy