Description
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.
That
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 and
other URI-safe CEL fragments can break out of the intended quoted string and
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
GCS
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);

- create and delete an object under another table's object prefix;

- 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. The issue is not limited to "another table".
In
the confirmed setup, once Apache Polaris returned credentials for the crafted
table,
the path restriction inside the configured bucket was effectively gone.

The practical effect is that temporary credentials for one crafted table
can be
broader than the table Polaris was asked to authorize, and can become
effectively bucket-wide within the configured bucket.



The current GCS testing used a Polaris principal with broad catalog
privileges for setup. A separate least-privilege Polaris RBAC variant
has not yet been tested on GCS. However, the storage-credential
broadening behavior itself has been confirmed on GCS.
Published: 2026-05-04
Score: 9.4 Critical
EPSS: n/a
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

Apache Polaris builds short‑lived GCS credentials by assembling a Credential Access Boundary that includes CEL conditions restricting access to a specific table’s storage path, but the code concatenates the bucket name with a table path derived from unescaped namespace and table identifiers. A crafted identifier containing a single quote or other CEL fragments can break out of the intended quoted string and alter the CEL logic, causing the access boundary to lose its path restriction and grant the delegated credentials full bucket access. This allows an attacker to list, read, create, and delete objects across any prefix in the configured bucket, including unrelated data and metadata.

Affected Systems

Apache Polaris, distributed by the Apache Software Foundation, is the affected product. No specific version information is supplied in the CVE data, so all released versions may be vulnerable until a patch is applied.

Risk and Exploitability

The CVSS base score of 9.4 classifies the flaw as critical; EPSS is not available, and it is not listed in CISA’s KEV catalog. The likely attack vector is by an actor that can provide a malicious namespace or table identifier to Polaris—such as through an API that creates or modifies tables—after which the attacker receives GCS credentials whose path restriction collapses, enabling broad access to the bucket. No additional privileges beyond the ability to submit the identifier are required, making the exploit feasible in environments where table creation or naming is exposed.

Generated by OpenCVE AI on May 4, 2026 at 19:35 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Upgrade Apache Polaris to the latest released version that contains the fix.
  • Sanitize all namespace and table identifiers to escape or reject unsafe characters before building Camel‑Case conditions, preventing CEL injection.
  • Restrict RBAC so that only trusted users can create or modify table names, limiting opportunities to supply malformed identifiers.
  • Apply the least‑privilege IAM permissions to the Service Account that generates credentials, restricting it to the intended bucket prefix.
  • Enable audit logging on GCS and review logs for anomalous credential usage or object access patterns.

Generated by OpenCVE AI on May 4, 2026 at 19:35 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Mon, 04 May 2026 20:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}


Mon, 04 May 2026 17:30:00 +0000

Type Values Removed Values Added
References

Mon, 04 May 2026 17:15:00 +0000

Type Values Removed Values Added
Description 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. That 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 and other URI-safe CEL fragments can break out of the intended quoted string and 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 GCS 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); - create and delete an object under another table's object prefix; - 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. The issue is not limited to "another table". In the confirmed setup, once Apache Polaris returned credentials for the crafted table, the path restriction inside the configured bucket was effectively gone. The practical effect is that temporary credentials for one crafted table can be broader than the table Polaris was asked to authorize, and can become effectively bucket-wide within the configured bucket. The current GCS testing used a Polaris principal with broad catalog privileges for setup. A separate least-privilege Polaris RBAC variant has not yet been tested on GCS. However, the storage-credential broadening behavior itself has been confirmed on GCS.
Title Apache Polaris: could broaden vended GCS credentials through unescaped identifier content in access-boundary CEL conditions
Weaknesses CWE-20
CWE-917
References
Metrics cvssV3_1

{'score': 9.9, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H'}

cvssV4_0

{'score': 9.4, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H'}


Subscriptions

No data.

cve-icon MITRE

Status: PUBLISHED

Assigner: apache

Published:

Updated: 2026-05-04T19:48:33.457Z

Reserved: 2026-04-30T14:30:15.047Z

Link: CVE-2026-42811

cve-icon Vulnrichment

Updated: 2026-05-04T16:38:55.378Z

cve-icon NVD

Status : Received

Published: 2026-05-04T17:16:26.677

Modified: 2026-05-04T17:16:26.677

Link: CVE-2026-42811

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-05-04T20:00:07Z

Weaknesses