Apache Polaris vulnerabilities

5 CVEs affecting Apache Polaris, 0 known to be exploited (CISA KEV), with EPSS scores. Latest: CVE-2026-64640, published 2026-08-06.

Highest priority

Known exploited (CISA KEV) first, then by EPSS exploit probability.

CVE-2026-42811, published 2026-05-04. Critical severity, CVSS 9.9. EPSS: 0.7% chance of exploitation in the next 30 days. 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…
CVE-2026-42810, published 2026-05-04. Critical severity, CVSS 9.9. EPSS: 0.7% chance of exploitation in the next 30 days. 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…
CVE-2026-42812, published 2026-05-04. Critical severity, CVSS 9.9. EPSS: 0.6% chance of exploitation in the next 30 days. In Apache Iceberg, the table's metadata files are control files: they tell readers which data files belong to the table and which table version to read. `write.metadata.path` is an optional table…
CVE-2026-42809, published 2026-05-04. Critical severity, CVSS 9.9. EPSS: 0.6% chance of exploitation in the next 30 days. Apache Polaris can issue broad temporary ("vended") storage credentials during staged table creation before the effective table location has been validated or durably reserved. Those temporary…
CVE-2026-64640, published 2026-08-06. Medium severity, CVSS 6.5. EPSS: 0.5% chance of exploitation in the next 30 days. 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…