Advisory record · GHSA-w76p-3cgp-qfcm

Apache Polaris has an Improper Input Validation issue

CVSS 9.4 CriticalCriticalEPSS 0.0037 · 30th percentile

Critical, because:

  • CVSS score 9.4: 9.0 or more.

How we decide what’s critical

Published by the GitHub Advisory Database at 4 May 2026, 18:30 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
org.apache.polaris:polaris-runtime-serviceMaven>=0.9.0, <1.4.11.4.1
Identifiers
GHSA-w76p-3cgp-qfcm · CVE-2026-42812
Weakness (CWE)
CWE-20 · CWE-284 · CWE-732 · CWE-863
Published
4 May 2026
Updated
31 Aug 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Apache Polaris versions 0.9.0 up to, but not including, 1.4.1 are affected. A user who can change table settings in a Polaris-managed catalog can cause Polaris to write table metadata to an attacker-chosen storage location by changing only the write.metadata.path property, bypassing the intended location check. When the catalog allows unstructured table locations and the allowed locations include the target, Polaris can persist that path and later issue temporary cloud storage credentials for it, exposing or corrupting data in that storage scope. Upgrade to Apache Polaris 1.4.1 or later.

Written 2 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
9.4 Critical 4.0 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 CNA (apache)
  • CISA KEV Not listed.
  • EPSS 0.0037, the 30th percentile, on 10 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:18 UTC First seen by agentprime
  2. 31 Oct 2026, 14:18 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.