Skip to main content
Vulnerability Database/CVE-2026-111670

CVE-2026-111670: ClickVisual Authorization Bypass Vulnerability

CVE-2026-111670 is an authorization bypass flaw in ClickVisual that allows low-privileged users to access restricted ClickHouse instances. This post explains its impact, affected versions, and mitigation steps.

Published:

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

CVE-2026-111670 Overview

ClickVisual through version 1.1.2 contains a missing authorization vulnerability [CWE-862] in the /api/v2/reports handlers. Authenticated low-privileged users can access ClickHouse instances they were not granted. Attackers iterate the instance-id parameter across ReportSourceDatabases, ReportSourceTables, ReportTableColumns, and WhereCheckRun handlers to enumerate schemas and infer row counts of restricted tables. The flaw is a cross-instance insecure direct object reference (IDOR) in the report module that bypasses tenant-level isolation controls.

Critical Impact

Authenticated users with the lowest ClickVisual role can enumerate database schemas and infer row counts across ClickHouse instances outside their authorization scope.

Affected Products

  • ClickVisual versions through 1.1.2
  • ClickVisual /api/v2/reports module handlers
  • ClickHouse instances registered as data sources in ClickVisual

Discovery Timeline

  • 2026-10-16 - CVE-2026-111670 published to NVD
  • 2026-10-19 - Last updated in NVD database

Technical Details for CVE-2026-111670

Vulnerability Analysis

ClickVisual exposes the report module through endpoints under /api/v2/reports. These handlers accept an instance-id query parameter that identifies a backend ClickHouse data source. The handler code at api/internal/api/apiv2/report/report.go and the metadata service at api/internal/service/report/metadata.go do not verify that the authenticated caller has permission to the targeted instance. Any authenticated session passes the authorization check for any instance-id value the backend recognizes.

The affected handlers include ReportSourceDatabases, which lists database names on an instance, ReportSourceTables, which lists tables within a database, ReportTableColumns, which returns column metadata, and WhereCheckRun, which executes a parameterized filter and returns a row count. Together they allow enumeration of schema structure and inference of row counts for restricted tables.

Root Cause

The root cause is missing authorization enforcement in the /api/v2/reports route handlers. The code trusts the caller's authentication state and dereferences the user-supplied instance-id without validating that the user has been granted access to that instance. This is a classic cross-instance IDOR pattern mapped to CWE-862: Missing Authorization.

Attack Vector

An attacker authenticates to ClickVisual with any valid low-privilege account. The attacker then iterates numeric values of the instance-id parameter against the four report handlers. Each successful response discloses database names, table names, column metadata, or row counts for instances the attacker was not granted. No user interaction is required and the attack is performed over the network against the ClickVisual API. See the HackMD technical analysis and the VulnCheck advisory for complete request examples.

Detect Identity Attacks the Moment Authentication Fails

Singularity™ Identity surfaces credential misuse, lateral movement, and privilege escalation in real time, so you can contain the breach before it spreads.

Stop Identity Attacks

Detection Methods for CVE-2026-111670

Indicators of Compromise

  • Repeated requests from a single authenticated session to /api/v2/reports/source-databases, /source-tables, /table-columns, or /where-check-run with sequentially changing instance-id values.
  • Access to instance-id values that fall outside the roles mapped to the requesting user in ClickVisual's RBAC configuration.
  • ClickHouse query logs showing schema introspection queries (SHOW DATABASES, SHOW TABLES, DESCRIBE) originating from the ClickVisual service account for instances the user should not reach.

Detection Strategies

  • Correlate ClickVisual application logs with user-to-instance authorization mappings and alert when a session accesses report endpoints for an unassigned instance-id.
  • Baseline each user's typical instance-id access set and flag deviations such as a sudden fan-out across many instance IDs.
  • Inspect reverse proxy or API gateway logs for enumeration patterns, specifically monotonically increasing instance-id values from one source IP within a short window.

Monitoring Recommendations

  • Enable verbose audit logging on all /api/v2/reports handlers, capturing user ID, session ID, and the instance-id parameter.
  • Forward ClickVisual and ClickHouse logs to a central analytics platform and build dashboards that pivot on user-to-instance access ratios.
  • Alert on high-volume calls to WhereCheckRun from accounts that have not previously issued row-count queries.

How to Mitigate CVE-2026-111670

Immediate Actions Required

  • Restrict network access to the ClickVisual UI and API to trusted operators until a patched release is deployed.
  • Audit all ClickVisual accounts and revoke sessions for users who do not require report-module access.
  • Review ClickHouse query logs for prior enumeration against instances the invoking user was not granted.

Patch Information

At the time of publication, the enriched CVE data lists no fixed version beyond 1.1.2. Monitor the ClickVisual GitHub repository and the VulnCheck advisory for a patched release. Any fix must add an instance-level authorization check in the handlers at api/internal/api/apiv2/report/report.go and the metadata service at api/internal/service/report/metadata.go.

Workarounds

  • Place ClickVisual behind an authenticating reverse proxy that enforces per-user allow-lists of instance-id values on /api/v2/reports/* paths.
  • Reduce the blast radius by segmenting sensitive ClickHouse instances into separate ClickVisual deployments per tenant or trust zone.
  • Remove the report module routes at the proxy layer if the reporting feature is not required in your deployment.
bash
# Example NGINX snippet: block /api/v2/reports until patched
location /api/v2/reports/ {
    return 403;
}

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.