Detections
Analytics

SCA: security update for org.apache.polaris:polaris-core (GHSA-vxgg-mqx2-3w59)

critical Tenable Self-Hosted Container Security Plugin ID 441553

Description

There are packages installed that are affected by a vulnerability referenced in the following CVE:

 - 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 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
 `f*.t1`, `f*.*`, `*.*`, and `foo.*` 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 `TABLE_CREATE`
 and `TABLE_WRITE_DATA` on `*`). In that setup, direct Polaris access to `foo.t1` 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 `foo.t1`. 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. (CVE-2026-42810)

Solution

Update the org.apache.polaris:polaris-core library and its related packages to version 1.4.1 or later.

See Also

https://github.com/advisories/GHSA-vxgg-mqx2-3w59

Plugin Details

Severity: Critical

ID: 441553

Version: Revision 1.4

Type: Local

Family: SCA Checks

Published: 5/8/2026

Updated: 7/2/2026

Supported Sensors: Tenable Cloud Security, Tenable Self-Hosted Container Security

Risk Information

VPR

Risk Factor: High

Score: 7

Percentile: 98.33

Vendor

Vendor Severity: Critical

CVSS v2

Risk Factor: High

Base Score: 9

Temporal Score: 6.7

Vector: CVSS2#AV:N/AC:L/Au:S/C:C/I:C/A:C

CVSS Score Source: CVE-2026-42810

CVSS v3

Risk Factor: Critical

Base Score: 9.9

Temporal Score: 8.6

Vector: CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

Temporal Vector: CVSS:3.0/E:U/RL:O/RC:C

CVSS v4

Risk Factor: Critical

Base Score: 9.4

Threat Score: 7.7

Threat Vector: CVSS:4.0/E:U

Vector: 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

Vulnerability Information

Exploit Ease: No known exploits are available

Patch Publication Date: 5/4/2026

Vulnerability Publication Date: 5/4/2026

Reference Information

CVE: CVE-2026-42810

cwe: CWE-20