ZeroDay Findings
Sign inSign up

Findings

CVE-2026-42810

Apache Polaris accepts literal characters in namespace and table names.

Published May 4, 2026 · corrected/updated Jun 17, 2026 · apache polaris · evidence confidence medium

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 conditions. In S3 IAM policy matching, is treated as a wildcard rather than as ordinary text. That means temporary credentials issued for one crafted table can match the storage path of a different table. In private testing against Polaris 1.4.0 using Polaris' AWS S3 temporary- credential path on both MinIO and real AWS S3, credentials returned for crafted tables such as , , , and could reach other tables' S3 locations. The confirmed behavior includes: - reading another table's metadata control file ([Iceberg metadata JSON]); - listing another table's exact S3 table prefix ([table prefix]); - and, when write delegation was returned for the crafted table, creating and deleting an object under another table's exact S3 table prefix. A control case using ordinary different names did not allow the same cross-table access. A least-privilege AWS S3 variant was also confirmed in which the attacker principal had no Polaris permissions on the victim table and only the minimal permissions required to create and use a crafted wildcard table (namespace-scoped and on ). In that setup, direct Polaris access to remained forbidden, but the attacker could still create and load , receive delegated S3 credentials, and use those credentials to list, read, create, and delete objects under . In Iceberg, the metadata JSON file is a control file: it tells readers which data files belong to the table, which snapshots exist, and which table version to read. So unauthorized access to it is already a meaningful confidentiality problem. The confirmed write-capable variant means the issue is not limited to disclosure.

Grounded briefings

Catalog interpretations for three audiences. Each brief cites ingested metadata and the original advisories below. They are not independent research and they do not invent exploit steps.

Executive

CVE-2026-42810 is a critical public vulnerability record for apache polaris. It is not currently listed in the CISA Known Exploited catalog. Check the linked vendor or CERT advisories for patch status. This summary is a catalog interpretation of the ingested metadata and cites the original advisories below.

System administrator

Identify whether apache polaris is in your estate, then compare installed versions with the affected ranges. Affected packages or ranges on record: apache/polaris. Check the linked vendor or CERT advisories for patch status. Prefer the vendor or distribution advisory linked in Sources before changing production systems. This is a catalog interpretation, not a runbook.

Security analyst

Signals on file: CVSS 9.4. It is not currently listed in the CISA Known Exploited catalog. Weakness classes: CWE-116, CWE-20. Sources contributing to this record: cve_org, nvd. Public exploit references, when present, are outbound links only and are not proof of active exploitation. This is a catalog interpretation of stored metadata.

Exploitation and remediation

  • Exploitation evidence

    Not listed as known exploited in CISA KEV. Not in the CISA KEV catalog.

  • Patch and remediation

    No required-action text is stored yet. Use the vendor or CERT links in Sources for patch availability.

  • Safe detection guidance

    Compare installed versions with the affected ranges below and verify the advisory from the original publisher. This site stores metadata and outbound links only; it does not ship exploit code or proof-of-concept payloads.

Code

The project this record applies to. Exploit listings stay in References.

No public source repository is identified for this product.

Timeline

Detection, updates, and resolution for this record.

  1. May 4, 2026 · NIST NVD

    Detected

    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 conditions. In S3 IAM policy matching, is treated as a wildcard rather than as ordinary text. That means temporary credentials issued for one crafted table can match

  2. Jun 17, 2026 · NIST NVD

    Updated

    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 conditions. In S3 IAM policy matching, is treated as a wildcard rather than as ordinary text. That means temporary credentials issued for one crafted table can match

Affected

  • cpe apache/polarisversion unspecified

Sources

  • CVE.orgVulnerability recordCVE-2026-42810

    Official CVE identifier

    cve.org
  • NIST NVDVulnerability recordCVE-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 conditions. In S3 IAM polic

    nvd.nist.gov

References