Cross-table storage access via wildcard policy injection
Published May 4, 2026 · Updated May 4, 2026
Improper input validation in Apache Polaris before 1.4.1 allows remote authenticated users to access other tables through vended S3 credentials. Polaris inserts literal asterisks from namespace or table names into S3 IAM resource patterns and prefix conditions, where IAM interprets them as wildcards. The issue requires AWS S3 credential vending and table-creation permissions; resulting credentials can read, create, or delete objects under another table's prefix.
Summary
What happened
Improper input validation in Apache Polaris before 1.4.1 allows remote authenticated users to access other tables through vended S3 credentials. Polaris inserts literal asterisks from namespace or table names into S3 IAM resource patterns and prefix conditions, where IAM interprets them as wildcards. The issue requires AWS S3 credential vending and table-creation permissions; resulting credentials can read, create, or delete objects under another table's prefix.
The record
- CVE
- CVE-2026-42810
- Published
- May 4, 2026
- Updated
- May 4, 2026
- Vendor
- The Apache Software Foundation
- Product
- Apache Polaris
- Classifications
- CWE-20, CWE-116, T1485, T1530
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- May 4, 2026CVE publishedPublication date reported by the CVE source.
- May 4, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <1.4.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo