ZeroDay Findings
Sign inSign up

Findings

Vulnerability · CVE-2026-42812

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.

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

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. is an optional table property that tells Polaris where to write those metadata files. For a table already registered in a Polaris-managed catalog, changing only that property through an -style settings change (not a row-level , , , or ) bypasses the commit-time branch that is supposed to revalidate storage locations. The full persisted / credential-vending variant requires the affected catalog to have , with broad enough to include the attacker-chosen target. is the admin-configured allowlist of storage paths that the catalog is allowed to use. Public project materials suggest that this flag is a real supported compatibility / layout mode, not just a contrived lab-only prerequisite. In that configuration, a user who can change table settings can cause Apache Polaris itself to write new table metadata to an attacker-chosen reachable storage location before the intended location-validation branch runs. If the later concrete-path validation also accepts that location, Polaris persists the resulting metadata path into stored table state. Later table-load and credential APIs can then return temporary cloud-storage credentials for the same location without revalidating it. In plain terms, Polaris can later hand out temporary storage access for the same attacker-chosen area. That attacker-chosen area does not need to be limited to the poisoned table's own files. If it is a broader storage prefix, another table's prefix, or, depending on configuration or provider behavior, even a bucket/container root, the resulting disclosure or corruption scope can extend to any data and metadata Polaris can reach there. The practical consequences are therefore similar to the staged-create credential-vending issue already discussed: data and metadata reachable in that storage scope can be exposed and, if write-capable credentials are late

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-42812 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, EPSS 0.6%. It is not currently listed in the CISA Known Exploited catalog. Weakness classes: CWE-20, CWE-284, CWE-732, CWE-863. Sources contributing to this record: cve_org, epss, 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 CISA KEV or VulnCheck KEV.

  • 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

    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. is an optional table property that tells Polaris where to write those metadata files. For a table already registered in a Polaris-managed catalog, changing only that property through an -style settings change (not a row-level , , , or ) bypasses t

  2. Jun 17, 2026 · NIST NVD

    Updated

    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. is an optional table property that tells Polaris where to write those metadata files. For a table already registered in a Polaris-managed catalog, changing only that property through an -style settings change (not a row-level , , , or ) bypasses t

Affected

  • cpe apache/polarisversion unspecified

Sources

  • CVE.orgVulnerability recordCVE-2026-42812

    Official CVE identifier

    cve.org
  • FIRST EPSSExploitation probabilityCVE-2026-42812

    30-day exploitation probability 0.6%

    first.org
  • NIST NVDVulnerability recordCVE-2026-42812

    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. is an optional table property that tells Polaris where to write those metadata files. For a table alr

    nvd.nist.gov

References