Incorrect Authorization Affecting apache-polaris package, versions <1.7.0-r0
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-MINIMOSLATEST-APACHEPOLARIS-18590626
- published8 Aug 2026
- disclosed6 Aug 2026
Introduced: 6 Aug 2026
NewCVE-2026-64640 (opens in a new tab)How to fix?
Upgrade Minimos:latest apache-polaris to version 1.7.0-r0 or higher.
NVD Description
Note: Versions mentioned in the description apply only to the upstream apache-polaris package and not the apache-polaris package as distributed by Minimos.
See How to fix? for Minimos:latest relevant fixed versions and status.
Apache Polaris did not consistently validate storage locations supplied during table and view registration.
An authenticated principal with permission to register a table or view could, depending on the affected release and registration path, cause Polaris to use the catalog's storage credentials to read a caller-selected Iceberg metadata file before verifying that the file was within the catalog's allowed storage locations.
If the catalog's underlying credentials could read an object outside that boundary, this could disclose limited information from the object.
Polaris could also accept registration metadata located within an allowed location that contained references to storage locations outside the allowed boundary.
This second condition did not itself cause Polaris to read the referenced external locations during registration.
The demonstrated impact is limited to confidentiality.
No unauthorized data modification or availability impact has been demonstrated.
The server-side read requires a deployment using S3 credential vending and an object outside the allowed locations that the catalog's underlying storage credentials can read.
Exploitation requires an authenticated principal with table- or view-registration privileges.
References
- https://www.cve.org/CVERecord?id=CVE-2026-64640
- https://github.com/advisories/GHSA-62q9-5g2h-5gxp
- https://osv.dev/vulnerability/MINI-fm65-hggj-v5j2
- https://osv.dev/vulnerability/CVE-2026-64640
- https://lists.apache.org/thread/scd8p9wy8b9j3om5wohbotpfycnmmjl4
- http://www.openwall.com/lists/oss-security/2026/08/06/7