Critical [CVE-2026-42811] In plain terms, Apache Polaris is supposed to issue short-lived GCS credentials that only work for one table's files, but a…

In plain terms, Apache Polaris is supposed to issue short-lived GCS credentials that

only work for one table's files, but a crafted namespace or table name can cause those credentials to work across the configured bucket instead.

Apache Polaris builds Google Cloud Storage downscoped credentials by creating a Credential Access Boundary (CAB) with CEL conditions that are intended to

restrict access to the requested table's storage path.

The relevant CEL string is built from the bucket name and the table path. table path is derived from namespace and table identifiers.

In current code, that path appears to be inserted into the CEL expression without escaping.

As a result, a namespace or table identifier containing a single quote other URI-safe CEL fragments can break out of the intended quoted string

change the meaning of the CEL condition.

In private testing against Polaris 1.4.0 on real Google Cloud Storage, it was confirmed that Polaris accepted a crafted identifier and returned delegated credentials whose CEL path restriction had effectively collapsed.

Those delegated credentials could then:

• list another table's object prefix;
• read another table's metadata control file (Iceberg metadata JSON);
• and also list, read, create, and delete objects under an unrelated

external prefix in the same bucket that was not part of any table path.

That last point is important.