Loading vulnerability…
Apache Polaris before version 1.4.1 contains a flaw in its delegated AWS S3 credential workflow. Polaris accepts literal asterisk characters in namespace and table names and later reuses those values unescaped when constructing temporary S3 IAM resource patterns and s3:prefix conditions for table-scoped access. Because AWS S3 IAM interprets the asterisk as a wildcard rather than a literal character, a user can create or access a crafted table name that causes the generated temporary policy to match storage prefixes belonging to other tables. Testing against Polaris 1.4.0 confirmed that crafted names could produce delegated credentials capable of crossing intended table boundaries on both MinIO and AWS S3 backends. Confirmed effects included reading another table's Iceberg metadata control file, listing another table's exact storage prefix, and, when write delegation was granted, creating and deleting objects under another table's storage prefix. The issue breaks the intended isolation between tables at the storage layer and bypasses Polaris authorization boundaries through overly broad delegated S3 policy generation.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
15 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A related Apache Polaris vulnerability mentioned only as one of the issues fixed in version 1.4.1; no technical details are provided in the content.
An input validation and output encoding flaw in Apache Polaris' delegated S3 credential mechanism allows low-privilege users to create table names containing wildcard asterisks, causing temporary IAM policies to grant overly broad access to other tables' S3 storage paths.
An Apache Polaris vulnerability where literal wildcard characters in namespace and table names are reused unescaped in S3 IAM resource patterns and prefix conditions, potentially broadening access scope.
An Apache Polaris vulnerability where literal wildcard characters in namespace and table names are reused unescaped in S3 IAM resource patterns and s3:prefix conditions, broadening credential scope.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.