CVE-2026-42810: Apache Polaris accepts literal `*` characters in namespace and table names

Q: How do I fix CVE-2026-42810?

polaris: upgrade to 1.4.1. Exact commands for each OS are on this page.

Q: Is CVE-2026-42810 being exploited?

CVE-2026-42810 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2026-42810 affect?

CVE-2026-42810 affects polaris. Severity is critical (CVSS 9.9). 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 `s

Q: How urgent is CVE-2026-42810?

Priority 49/100. Critical severity; On your watchlist

This month

CRITICAL 9.9WATCHLISTUPGRADE

CVE-2026-42810 is a critical-severity flaw (CVSS 9.9) affecting polaris. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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 diffe

Why this priority

Critical severity
On your watchlist

A fixed release or distro patch exists.

Risk facts

CVSS score	9.9 (Critical)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	Low
User interaction	None
EPSS exploit chance	0.4% (top 63%)
CISA exploited list	No
Weakness	CWE-20, CWE-116
Published	2026-05-04
Last modified	2026-10-26

Publisher (CNA): Apache Software Foundation · Vendor: apache

Last updated 2026-10-26 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2026-05-04 17:16 UTCPublished CVE record published
2026-10-26 19:10 UTCUpdated Record last modified

apache polaris UPGRADE

Affected: < 1.4.1

Fixed in: 1.4.1

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy polaris || rpm -q polaris || polaris --version

2. UPGRADE to 1.4.1 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade polaris

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade polaris

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-42810?

polaris: upgrade to 1.4.1. Exact commands for each OS are on this page.

Is CVE-2026-42810 being exploited?

CVE-2026-42810 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-42810 affect?

CVE-2026-42810 affects polaris. Severity is critical (CVSS 9.9). 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 `s

How urgent is CVE-2026-42810?

Priority 49/100. Critical severity; On your watchlist

Related CVEs

CVE-2026-42811 CRITICAL 9.9 UPGRADE In plain terms, Apache Polaris is supposed to issue short-lived GCS credentials that only work for one table's
CVE-2026-42809 CRITICAL 9.9 UPGRADE Apache Polaris can issue broad temporary ("vended") storage credentials during staged table creation before th
CVE-2026-42812 CRITICAL 9.9 UPGRADE In Apache Iceberg, the table's metadata files are control files: they tell readers which data files belong to
CVE-2026-64640 MEDIUM 6.5 UPGRADE Apache Polaris did not consistently validate storage locations supplied during table and view registration. A

References

← Back to latest CVEs