CVE-2026-63080
Received Received - Intake

SQL Injection in Aptabase ClickHouse Backend

Publication date: 2026-07-21

Last updated on: 2026-07-21

Assigner: VulnCheck

Description
Aptabase through commit 5a89368 contains a SQL injection vulnerability in the ClickHouse query backend that allows authenticated attackers to read event data across all tenants by injecting unsanitized filter parameters into Liquid SQL templates. Attackers can supply malicious values through EventName, CountryCode, OsName, DeviceModel, AppVersion, or SessionId parameters to inject a UNION ALL statement that bypasses the app_id tenant isolation filter across thirteen of the fifteen stats API endpoints.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-07-21
Last Modified
2026-07-21
Generated
2026-07-22
AI Q&A
2026-07-22
EPSS Evaluated
N/A
NVD
CVE-2026-63080

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
aptabase aptabase *

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-89 The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

Aptabase has a SQL injection flaw in its ClickHouse query backend. Authenticated attackers can exploit this by injecting malicious values into parameters like EventName or CountryCode. This bypasses tenant isolation, allowing unauthorized access to event data across all tenants.

Detection Guidance

To detect this SQL injection vulnerability in Aptabase, monitor API endpoints for suspicious query patterns. Check for UNION ALL statements in requests to stats endpoints with parameters like EventName, CountryCode, OsName, DeviceModel, AppVersion, or SessionId. Inspect logs for malformed queries or unexpected data exposure across tenants.

Impact Analysis

If you use Aptabase, attackers could steal sensitive event data from other tenants. This may lead to data breaches, privacy violations, or unauthorized access to user information. The impact depends on the data collected by your application.

Compliance Impact

This vulnerability could violate GDPR by exposing personal data without consent and HIPAA by leaking protected health information. Non-compliance may result in fines, legal penalties, and reputational damage due to unauthorized data access.

Mitigation Strategies

Immediately update Aptabase to the latest commit or version that patches the SQL injection flaw. Implement input validation for all API parameters, especially those used in Liquid SQL templates. Restrict database user permissions to limit read access across tenants. Monitor for unauthorized data access attempts.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-63080. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart