Skip to content
Cloud

CVE-2026-42812

9.4
Critical
EPSS 0.36%Patch availableMay 5, 2026

Polaris metadata path abuse enables writes to attacker-controlled storage.

common questions

Is CVE-2026-42812 being exploited?

Not confirmed. CVE-2026-42812 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.36% probability of exploitation in the next 30 days.

How severe is CVE-2026-42812?

CVE-2026-42812 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-42812?

Yes. A fix has been recorded for CVE-2026-42812. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-42812 affect?

CVE-2026-42812 affects Polaris catalog, Apache Iceberg, Cloud storage backends configured with write.metadata.path. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-42812?

Tighten write.metadata.path validation and location checks; monitor changes; patch when available.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Polaris catalogApache IcebergCloud storage backends configured with write.metadata.path
impact

Writes table metadata to attacker-chosen storage, enabling data exposure, modification, or credential vending.

action required

Immediate action required

affected versions
Apache Software Foundation Apache Polaris
  • 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.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free