Security Bulletin 2026-05-03-01

Abstract​

Multiple vulnerabilities in Apache Polaris allowed authenticated users to escalate storage access or write unauthorized metadata in Dremio Open Catalog.

CVSS Qualitative Rating​

• Important
• CVSSv4.0
  • Score: 9.4
  • 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
• CVE-2026-42809: Staged table creation minted broad temporary storage credentials for an attacker-chosen location
• CVE-2026-42810: Literal wildcard characters in namespace and table names were reused unescaped in S3 IAM resource patterns
• CVE-2026-42811: Crafted namespace or table names allowed short-lived GCS credentials to work across the configured bucket
• CVE-2026-42812: No protection on write.metadata.path allowed unauthorized metadata writes

Affected Releases​

• Dremio 26.0.0 through 26.1.6

Problem Description​

In Affected Releases, four vulnerabilities within the Apache Polaris component used by Dremio Open Catalog could allow an authenticated low-privileged user to escalate their storage access or write unauthorized metadata:

• CVE-2026-42809: An authenticated low-privileged user could abuse Polaris staged table creation to mint broad temporary storage credentials for an attacker-chosen location before Polaris validated that location.
• CVE-2026-42810: Polaris accepted literal * characters in namespace and table names. When Polaris later built temporary S3 access policies for delegated table access, those characters were reused unescaped in S3 IAM resource patterns and s3:prefix conditions.
• CVE-2026-42811: Crafted namespace or table names could cause short-lived GCS credentials, which are intended to work only for one table's files, to work across the configured bucket instead.
• CVE-2026-42812: There was no protection on write.metadata.path, which could allow unauthorized metadata writes.

Resolution Actions​

Upgrade to a Fixed Release that resolves the issue.

Fixed Releases​

• Dremio 26.1.7 and above