# CVE-2026-97395: Server-side request forgery in Apache Polaris

> Authorized table writers can redirect server-side storage requests to attacker endpoints, exposing credentials and data in Apache Polaris deployments.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 29 Sep 2026
- **Updated:** 1 Oct 2026
- **Also known as:** GHSA-848v-j2j6-p92w, MINI-356j-55j2-jvc4, MINI-4cwf-5jpf-3hq3, MINI-9qfg-grmh-jrqq, MINI-qrp5-f5g4-73x4

## What is CVE-2026-97395?

CVE-2026-97395 is a high-severity server-side request forgery vulnerability in Apache Polaris, published on 29 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Apache Polaris allows an authenticated principal with permission to create or update Iceberg table properties to set FileIO client settings such as s3.endpoint in table metadata.

In versions < 1.8.0, when Polaris performs server-side Iceberg operations, including commits and purges, it may use those settings to construct its (server-side) FileIO client. If the catalog storage configuration does not override the endpoint, Polaris can send storage requests to a host chosen by the table writer, using credentials scoped to the operation.

This can redirect server-side storage traffic and expose request authentication material to the chosen endpoint. Deployments are affected when table writers are not trusted to configure server-side storage endpoints.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2026-97395?


## How do I fix CVE-2026-97395?

Upgrade to a fixed version.

## Is CVE-2026-97395 being exploited?

There is no known exploitation of CVE-2026-97395 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-97395 and fix it if it is affected.

What it is: CVE-2026-97395 is a high-severity server-side request forgery vulnerability in Apache Polaris, published on 29 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-97395 in the wild and no public exploit code.

Affected product: Apache Polaris. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-97395/ (Markdown: https://insights.sbomify.com/CVE-2026-97395/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-97395
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-97395
- OSV: https://osv.dev/vulnerability/CVE-2026-97395

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-97395/
Summaries are generated and may contain mistakes; the official description above is the record.