CVE-2026-42811: Polaris core Apache Polaris Has An Improper Vulnerability

CRITICAL
Advisory Identifier: GHSA-fc3h-c6h7-r83j
CVSS 9.9
CWE-20
Published
Advisory Summary

CVE-2026-42811 is a CRITICAL (CVSS 9.9) apache polaris has an improper vulnerability (CWE-20: Improper Input Validation) affecting Polaris core libraries in the Maven ecosystem. The issue involves apache polaris has an improper input validation issue. Remediation is available by upgrading affected packages to version 1.4.1.

CVE-2026-42811 at a Glance

CVE Identifier CVE-2026-42811
GHSA Identifier GHSA-fc3h-c6h7-r83j
Severity CRITICAL
CVSS v3.1 Base Score 9.9
CWE Classification CWE-20: Improper Input Validation
Affected Product Polaris core
Package Ecosystem Maven
Published Date
Last Updated

Security Impact

CVSS: 9.9

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required Low (PR:L)
User Interaction None (UI:N)
Scope Changed (S:C)
Confidentiality High (C:H)
Integrity High (I:H)
Availability High (A:H)

How to Fix CVE-2026-42811

To remediate this vulnerability, upgrade all affected Polaris core dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

org.apache.polaris:polaris-core fixed: 1.4.1
<dependency>
    <groupId>org.apache.polaris</groupId>
    <artifactId>polaris-core</artifactId>
    <version>1.4.1</version>
</dependency>
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

mvn dependency:tree -Dincludes=org.apache.polaris

How to Check if You Are Affected

To determine whether your Java application is affected by CVE-2026-42811, inspect your build dependencies using the Maven Dependency Plugin:

mvn dependency:tree -Dincludes=org.apache.polaris

Analyze the terminal output to locate any version of Polaris core in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 1.4.1), your application is affected.

Note: The mvn dependency:tree -Dincludes=org.apache.polaris command inspects the resolved dependency graph declared in your project's POM files; it does not perform automated security scanning or inspect runtime dynamic classpaths. Always verify runtime container classpaths and shaded JARs.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-20: Improper Input Validation, where the product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly. In Polaris core, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

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 the configured bucket instead. Apache Polaris builds Google Cloud Storage downscoped credentials by creating a Credential Access Boundary (CAB) with CEL conditions that are intended to restrict access to the requested table's storage path. The relevant CEL string is built from the bucket name and the table path. That table path is derived from namespace and table identifiers. In current code, that path appears to be inserted into the CEL expression without escaping. As a result, a namespace or table identifier containing a single quote and other URI-safe CEL fragments can break out of the intended quoted string and change the meaning of the CEL condition. In private testing against Polaris 1.4.0 on real Google Cloud Storage, it was confirmed that Polaris accepted a crafted identifier and returned delegated GCS credentials whose CEL path restriction had effectively collapsed. Those delegated credentials could then: - list another table's object prefix - read another table's metadata control file (Iceberg metadata JSON); - create and delete an object under another table's object prefix; - and also list, read, create, and delete objects under an unrelated external prefix in the same bucket that was not part of any table path. That last point is important. The issue is not limited to "another table". In the confirmed setup, once Apache Polaris returned credentials for the crafted table, the path restriction inside the configured bucket was effectively gone. The practical effect is that temporary credentials for one crafted table can be broader than the table Polaris was asked to authorize, and can become effectively bucket-wide within the configured bucket. The current GCS testing used a Polaris principal with broad catalog privileges for setup. A separate least-privilege Polaris RBAC variant has not yet been tested on GCS. However, the storage-credential broadening behavior itself has been confirmed on GCS.

CVE-2026-42811 Affected Polaris core Versions

1 component(s)
Fixed Versions:
1.4.1
Product / Package Ecosystem Affected Versions Fixed Version
org.apache.polaris:polaris-core
Maven
< 1.4.1
1.4.1

References

Frequently Asked Questions

What is CVE-2026-42811?
CVE-2026-42811 is a security vulnerability in Polaris core involving Apache Polaris has an Improper Input Validation issue under CWE-20: Improper Input Validation.
Which Polaris core versions are affected?
Affected versions include releases prior to 1.4.1 across affected packages: org.apache.polaris:polaris-core.
What version fixes CVE-2026-42811?
Upgrading to 1.4.1 (or the latest patched release for your respective branch) resolves the vulnerability.
Is polaris-core affected?
Yes, org.apache.polaris:polaris-core is affected in releases prior to 1.4.1. Upgrade your dependency to 1.4.1 or later.
What is the CVSS score of CVE-2026-42811?
CVE-2026-42811 has a CVSS v3.1 base score of 9.9 (CRITICAL) with vector string CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H.
What CWE is associated with CVE-2026-42811?
CVE-2026-42811 is classified under CWE-20: Improper Input Validation (The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly.).
How can I check Maven dependencies for CVE-2026-42811?
Run the dependency tree command: 'mvn dependency:tree -Dincludes=org.apache.polaris'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-fc3h-c6h7-r83j",
  "modified" : "2026-05-08T17:58:22Z",
  "published" : "2026-05-04T18:30:31Z",
  "aliases" : [ "CVE-2026-42811" ],
  "summary" : "Apache Polaris has an Improper Input Validation issue",
  "details" : "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 the configured bucket instead.\n\nApache Polaris builds Google Cloud Storage downscoped credentials by creating a Credential Access Boundary (CAB) with CEL conditions that are intended to restrict access to the requested table's storage path.\n\nThe relevant CEL string is built from the bucket name and the table path. That table path is derived from namespace and table identifiers. In current code, that path appears to be inserted into the CEL expression without escaping.\n\nAs a result, a namespace or table identifier containing a single quote and other URI-safe CEL fragments can break out of the intended quoted string and change the meaning of the CEL condition.\n\nIn private testing against Polaris 1.4.0 on real Google Cloud Storage, it was confirmed that Polaris accepted a crafted identifier and returned delegated GCS credentials whose CEL path restriction had effectively collapsed.\n\nThose delegated credentials could then:\n- list another table's object prefix\n- read another table's metadata control file (Iceberg metadata JSON);\n- create and delete an object under another table's object prefix;\n- and also list, read, create, and delete objects under an unrelated external prefix in the same bucket that was not part of any table path.\n\nThat last point is important. The issue is not limited to \"another table\". In the confirmed setup, once Apache Polaris returned credentials for the crafted table, the path restriction inside the configured bucket was effectively gone.\n\nThe practical effect is that temporary credentials for one crafted table can be broader than the table Polaris was asked to authorize, and can become effectively bucket-wide within the configured bucket.\n\nThe current GCS testing used a Polaris principal with broad catalog privileges for setup. A separate least-privilege Polaris RBAC variant has not yet been tested on GCS. However, the storage-credential broadening behavior itself has been confirmed on GCS.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H"
  }, {
    "type" : "CVSS_V4",
    "score" : "CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Maven",
      "name" : "org.apache.polaris:polaris-core"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "1.4.1"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-42811"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/apache/polaris/commit/f86ce44053e52f77331d212106a9ab6b83c5cace"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/apache/polaris"
  }, {
    "type" : "WEB",
    "url" : "https://lists.apache.org/thread/hovn5hmkj9wj7v9cd8sn67svg03klgvg"
  }, {
    "type" : "WEB",
    "url" : "http://www.openwall.com/lists/oss-security/2026/05/02/12"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-20" ],
    "severity" : "CRITICAL",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-05-08T17:58:22Z",
    "nvd_published_at" : "2026-05-04T17:16:26Z"
  }
}