Trino: Iceberg REST catalog static and vended credentials are accessible via query JSON

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

7.7 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N

EPSS

• CVE-2026-34214: 0.20% estimated exploitation activity in the next 30 days; percentile 10.36 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary 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. Details Iceberg REST catalog typically needs access to object storage. This access can be configured in multiple different ways. When storage access is achieved by static credentials (e.g. AWS S3 access key) or vended credentials (temporary access key). Query JSON is a query visualization and performance troubleshooting facility. It includes serialized query plan and handles for table writes or execution of table procedures. A user that submitted a query has access to query JSON for their query. Query JSON is available from Trino UI or via /ui/api/query/«queryid» and /v1/query/«queryid» endpoints. The storage credentials are stored in those handles when performing write operations, or table maintenance operations. They are serialized in query JSON. A user with write access to data in Iceberg connector…

Published by the source

29 Mar 2026, 15:13 UTC

Last modified by the source

31 Mar 2026, 18:51 UTC

Source last checked

26 Oct 2026, 16:45 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-x27p-5f68-m644

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-34214

Advisory: Trino: Iceberg REST catalog static and vended credentials are accessible via query JSON
IDs: CVE-2026-34214, GHSA-x27p-5f68-m644
Record: https://patchnext.com/advisories/cve-2026-34214 (revision 1, source checked 26 Oct 2026, 16:45 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.7)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: io.trino:trino-iceberg 480. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven io.trino:trino-iceberg: affected >= 439, < 480; fixed in 480

## Suggested inspection (read-only)
- Maven io.trino:trino-iceberg: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on io.trino:trino-iceberg.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-x27p-5f68-m644 (GitHub-reviewed advisory GHSA-x27p-5f68-m644 lists affected ranges: Maven io.trino:trino-iceberg >=439 <480)

Commands are suggestions: review each one before running it.