CVE-2026-42810
Cross-table S3 access in Polaris via wildcard table names; exposes data/metadata.
Is CVE-2026-42810 being exploited?
Not confirmed. CVE-2026-42810 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.43% probability of exploitation in the next 30 days.
How severe is CVE-2026-42810?
CVE-2026-42810 is rated Critical with a CVSS score of 9.4. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-42810?
Yes. A fix has been recorded for CVE-2026-42810. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-42810 affect?
CVE-2026-42810 affects Apache Polaris. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-42810?
Patch when available; disable wildcard table names; rotate credentials.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Unauthorized read/list/write access to other tables' S3 prefixes via crafted tables.
Patch when possible
- affected< 1.4.1
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.