Skip to content
VulniPulse
Critical9.4Apache Software Foundation

Critical [CVE-2026-42809] Apache Polaris can issue broad temporary ("vended") storage credentials during staged table creation before the effective table…

This critical-severity Apache Software Foundation advisory covers CVE-2026-42809 affecting Apache Polaris.

CVE-2026-42809 Published May 4, 2026Updated by vendor Jun 17, 2026
Affected products & platforms
Apache Software FoundationUnclassified
Open vendor advisory

Android app · Google Play

Monitor future Apache Software Foundation CVEs from your phone.

Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 32 official vendor sources and 160+ reviewed platform categories.

Matching phone alertsOptional email delivery

Summary

Apache Polaris can issue broad temporary ("vended") storage credentials during staged

table creation before the effective table location has been validated or durably reserved.

Those temporary credentials are meant to limit the scope of

accessible table data and metadata, but this scope limitation becomes attacker-

In the confirmed variant, if the caller supplies a custom `location` during stage create and requests credential vending, Apache Polaris uses that location to

construct delegated storage credentials immediately. The stage-create path

itself neither runs the normal location validation nor the overlap checks before those credentials are issued.

`write.data.path` / `write.metadata.path` in the request properties feeds

those location overrides into the same effective table location set used for Those fields are secondary to the main custom-`location`

be

Affected versions

No affected-version range was extracted from the source record. The vendor advisory is authoritative — check it before change work.

Official advisory · medium-confidence parse· fetched 2 months ago·verify at source

Fixed versions

No fixed release is recorded yet. That does not prove no patch exists — confirm against the vendor advisory.

Official advisory · medium-confidence parse· fetched 2 months ago·verify at source

Mitigation

The source record does not include mitigation steps. That is not a statement that no fix exists — read the vendor advisory below for the authoritative guidance.

Official advisory · medium-confidence parse· fetched 2 months ago·verify at source

Discussion(0)

No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.

Sign in to join the discussion.