CVE-2026-64640
MediumCVSS 6.5Exploitation Probability (EPSS)
Low risk42th percentile - higher than 42% of all known CVEs
Summary
Apache Polaris did not consistently validate storage locations supplied during table and view registration. An authenticated principal with registration permissions could cause Polaris to use the catalog's storage credentials to read a caller-selected Iceberg metadata file before verifying it was within allowed locations, potentially disclosing limited information. Polaris could also accept registration metadata with references to external locations, but this did not cause reads.
Risk Assessment
Risk of disclosure of confidential data from objects stored outside allowed locations, potentially compromising information confidentiality.
Recommendation
Update Apache Polaris to a patched version and implement strict validation of storage locations during table and view registration.
Other vulnerabilities in Apache Polaris
See all- CVE-2026-42812Critical
Apache Polaris contains a vulnerability allowing a user who can change table settings to bypass storage location validation during metadata writes. Changing only the `write.metadata.path` property via an `ALTER TABLE`-style change skips the commit-time validation branch, potentially causing Polaris to write metadata to an attacker-chosen location and later vend credentials for that location.
- CVE-2026-42811Critical
Apache Polaris issues short-lived GCS credentials with a CEL-based path restriction built without escaping the namespace or table identifier. A crafted identifier containing a single quote and CEL fragments can break out of the quoted string and broaden the credentials to the entire configured bucket. This was confirmed in testing against Polaris 1.4.0 with real Google Cloud Storage.
- CVE-2026-42810Critical
Apache Polaris accepts literal `*` characters in namespace and table names and later reuses them unescaped in S3 IAM resource patterns and `s3:prefix` conditions. Because `*` acts as a wildcard in S3 IAM policy matching, temporary credentials issued for a crafted table (e.g. `f*.t1`, `*.*`) can match the storage path of a different table. Confirmed behavior includes reading another table's Iceberg metadata JSON, listing its exact S3 prefix, and creating or deleting objects under it when write delegation is returned.
- CVE-2026-42809Critical
Apache Polaris issues broad temporary (vended) storage credentials during staged table creation before the effective table location has been validated or durably reserved. An attacker can supply a custom location (or write.data.path/write.metadata.path), making the credential scope attacker-directed.
- CVE-2026-97395High
Apache Polaris allows an authenticated principal with permission to create or update Iceberg table properties to set FileIO client settings such as s3.endpoint in table metadata. In versions < 1.8.0, Polaris may use these settings to construct its server-side FileIO client, potentially redirecting storage traffic to a host chosen by the table writer and exposing authentication material.
Original NVD description (English source)
Apache Polaris did not consistently validate storage locations supplied during table and view registration. An authenticated principal with permission to register a table or view could, depending on the affected release and registration path, cause Polaris to use the catalog's storage credentials to read a caller-selected Iceberg metadata file before verifying that the file was within the catalog's allowed storage locations. If the catalog's underlying credentials could read an object outside that boundary, this could disclose limited information from the object. Polaris could also accept registration metadata located within an allowed location that contained references to storage locations outside the allowed boundary. This second condition did not itself cause Polaris to read the referenced external locations during registration. The demonstrated impact is limited to confidentiality. No unauthorized data modification or availability impact has been demonstrated. The server-side read requires a deployment using S3 credential vending and an object outside the allowed locations that the catalog's underlying storage credentials can read. Exploitation requires an authenticated principal with table- or view-registration privileges.
Vulnerability data from NVD (NIST) · CISA KEV · EPSS