# CVE-2026-34214: Trino: Iceberg REST catalog static and vended credentials are accessible via query JSON

> Users with SQL write privileges can access Iceberg REST catalog static or vended credentials via query JSON, exposing sensitive authentication keys.

- **Severity:** High 7.7 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/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:** 31 Mar 2026
- **Updated:** 31 Mar 2026
- **Also known as:** GHSA-x27p-5f68-m644

## What is CVE-2026-34214?

CVE-2026-34214 is a high-severity vulnerability in trinodb trino, published on 31 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Trino is a distributed SQL query engine for big data analytics. From version 439 to before version 480, Iceberg connector REST catalog static credentials (access key) or vended credentials (temporary access key) are accessible to users that have write privilege on SQL level. This issue has been patched in version 480.

Weakness: CWE-312 (Cleartext Storage of Sensitive Information), CWE-212 (Improper Removal of Sensitive Information Before Storage or Transfer)

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

2 open source packages ship an affected version, including io.trino:trino-iceberg. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `io.trino:trino-iceberg` | Maven | From 439 | 480 |
| `io.trino:trino-iceberg` | Maven | From 439 | 480 |

Products: Trino Trino.

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

Upgrade io.trino:trino-iceberg to 480 or later.

## Is CVE-2026-34214 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-34214 is a high-severity vulnerability in trinodb trino, published on 31 Mar 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-34214 in the wild and no public exploit code.

Affected packages and fixed versions:
- io.trino:trino-iceberg (Maven): affected from 439; fixed in 480
- io.trino:trino-iceberg (Maven): affected from 439; fixed in 480

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-34214/ (Markdown: https://insights.sbomify.com/CVE-2026-34214/index.md)
```

## Sources

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

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