CVE-2026-64640
MediumCVSS 6.5Exploitation Probability (EPSS)
Low risk29th percentile - higher than 29% 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-42811Critical
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.
- CVE-2026-42810Critical
Apache Polaris accepts literal `*` characters in namespace and table names. When it later builds temporary S3 access policies for delegated table access, those same characters appear to be reused unescaped in S3 IAM resource patterns.
- CVE-2026-42809Critical
Apache Polaris can issue broad temporary ('vended') storage credentials during staged table creation before the effective table location has been validated or durably reserved. An attacker can choose a reachable target location, leading to unauthorized access to table data and metadata.
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.