Live › vulnerability › CVE-2026-73322
In Apache Pinot's single-stage query engine, the lookup() function reads a dimension table named in a string literal, and the broker's access check never covers that table. An authenticated user with access to any one table can read columns and arbitrary rows from any dimension table, bypassing row-level security filters.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-30 19:25 UTC. All times on this page are UTC.
Clusters running Apache Pinot through 1.5.1 with broker access control enabled and dimension tables holding restricted data. The multi-stage query engine is not affected, so deployments using only that engine can skip it. Anyone running a Pinot version above 1.5.1 is not affected.
No product ranges from the sources yet.
1.5.1.1.6.0.Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
Incorrect Authorization vulnerability in the single-stage query engine of Apache Pinot.
When broker access control is enabled, the single-stage query engine authorizes only the table named in the query's FROM clause. The lookup() transform function identifies its dimension table with a string literal argument rather than through the FROM clause, so that table was never included in the authorization check. An authenticated user who is authorized for at least one table can therefore read columns from any dimension table in the cluster, including tables they have no access to, and can retrieve arbitrary rows of it by supplying primary key values directly. Per-principal row-level security filters configured on the dimension table are likewise not applied.
The multi-stage query engine is not affected.
This issue affects Apache Pinot: through 1.5.1
Users are recommended to upgrade to version 1.6.0, which fixes this issue.
This page as .md · .json · in your agent: get_signal("CVE-2026-73322")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.