Lucene search
+L

13 matches found

NVD
NVD
added 2026/08/06 9:16 a.m.10 views

CVE-2026-64640

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...

6.5CVSS0.00359EPSS
SaveExploits1References2
OSV
OSV
added 2026/08/06 9:08 a.m.21 views

CVE-2026-64640 Apache Polaris: register endpoint reads attacker-controlled storage location before allowed-locations validation

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...

5.3CVSS5.3AI score
SaveExploits0References4
CVE
CVE
added 2026/08/06 9:08 a.m.55 views

CVE-2026-64640

Apache Polaris is affected by a storage-location validation flaw during table/view registration. An authenticated user with table- or view-registration privileges could trigger Polaris to use the catalog’s storage credentials to read a caller-supplied Iceberg metadata file before confirming it li...

6.5CVSS5.4AI score0.00359EPSS
SaveExploits1References2Affected Software1
Cvelist
Cvelist
added 2026/08/06 9:08 a.m.41 views

CVE-2026-64640 Apache Polaris: register endpoint reads attacker-controlled storage location before allowed-locations validation

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...

5.3CVSS0.00359EPSS
SaveExploits1References1
EUVD
EUVD
added 2026/08/06 9:08 a.m.12 views

EUVD-2026-53835

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...

6.5CVSS5.4AI score0.00359EPSS
SaveExploits1References1
RedhatCVE
RedhatCVE
added 2026/06/05 7:16 p.m.13 views

CVE-2026-42810

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 and s3:prefix conditions. In S3 IAM policy matching, is treated as ...

9.9CVSS5.4AI score0.00425EPSS
SaveExploits0References1
Vulnrichment
Vulnrichment
added 2026/05/04 4:48 p.m.16 views

CVE-2026-42810 Apache Polaris: could broaden vended S3 credentials through wildcard-bearing namespace or table names

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 and s3:prefix conditions. In S3 IAM policy matching, is treated as ...

9.9CVSS5.8AI score0.00425EPSS
SaveExploits0References1
ATTACKERKB
ATTACKERKB
added 2026/05/04 4:48 p.m.8 views

CVE-2026-42810

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 and s3:prefix conditions. In S3 IAM policy matching, is treated as ...

9.9CVSS5.8AI score0.00425EPSS
SaveExploits0References2
Cvelist
Cvelist
added 2026/05/04 4:48 p.m.46 views

CVE-2026-42810 Apache Polaris: could broaden vended S3 credentials through wildcard-bearing namespace or table names

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 and s3:prefix conditions. In S3 IAM policy matching, is treated as ...

9.9CVSS0.00425EPSS
SaveExploits0References1
EUVD
EUVD
added 2026/05/04 4:48 p.m.15 views

EUVD-2026-27035

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 and s3:prefix conditions. In S3 IAM policy matching, is treated as ...

9.9CVSS5.8AI score0.00425EPSS
SaveExploits0References1
OSV
OSV
added 2026/05/04 4:48 p.m.12 views

CVE-2026-42810 Apache Polaris: could broaden vended S3 credentials through wildcard-bearing namespace or table names

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 and s3:prefix conditions. In S3 IAM policy matching, is treated as ...

9.4CVSS6AI score
SaveExploits0References4
CVE
CVE
added 2026/05/04 4:48 p.m.78 views

CVE-2026-42810

CVE-2026-42810 affects Apache Polaris. The issue arises because Polaris accepts literal ‘’ characters in namespace and table names, and these unescaped characters are reused in temporary S3 access policies for delegated table access. In S3 IAM policy matching, ‘ ’ is treated as a wildcard, allowi...

9.9CVSS5.8AI score0.00425EPSS
SaveExploits0References2Affected Software1
EUVD
EUVD
added 2026/05/04 4:19 p.m.20 views

EUVD-2026-27039

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 property that tells Polaris where to write those metadata files. For a table already registered in a...

9.9CVSS5.8AI score0.00365EPSS
SaveExploits0References1
Rows per page
Query Builder