# Apache Polaris did not consistently validate storage locations supplied during table and view registration.

Advisory record · `PYSEC-2026-3623`

- **Identifiers:** `PYSEC-2026-3623` · `CVE-2026-64640`
- **State:** Confirmed
- **Severity:** CVSS 5.3 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-863](https://cwe.mitre.org/data/definitions/863.html)
- **Tags:** [Broken access control](https://agentprime.io/advisories/tag/access-control.md)
- **Published:** 6 Aug 2026
- **Updated:** 7 Aug 2026
- **Reviewed by a person:** No

Published by OSV at 6 Aug 2026, 09:16 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `apache-polaris` (PyPI): affected `<1.7.0`; fixed in `1.7.0`

## Machine-written summary

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

> Apache Polaris (PyPI apache-polaris, versions before 1.7.0) did not consistently validate storage locations supplied when registering tables and views. An authenticated principal with table or view registration privileges could make Polaris read a caller-selected Iceberg metadata file using the catalog's storage credentials before the location check, which could disclose limited information from objects outside allowed locations in S3 credential-vending deployments. Upgrade to apache-polaris 1.7.0 or later. The source gives no other workaround.

Written 5 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

- 5.3 Medium, CVSS 4.0: `CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/S:N/U:Clear`, from CNA (apache)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0049, the 42nd percentile, on 18 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 14:40 UTC: First seen by agentprime
- 31 Oct 2026, 14:40 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/PYSEC-2026-3623)

## Sources

- [OSV: PYSEC-2026-3623](https://osv.dev/vulnerability/PYSEC-2026-3623)
- <http://www.openwall.com/lists/oss-security/2026/08/06/7>
- <https://lists.apache.org/thread/scd8p9wy8b9j3om5wohbotpfycnmmjl4>

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.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/PYSEC-2026-3623>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/PYSEC-2026-3623/>. Everything for agents: <https://agentprime.io/llms.txt>.
