What is the CVSS score of CVE-2026-34214?

CVE-2026-34214 has a CVSS 3.1 base score of 6.5 (Medium). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N. EPSS exploitation probability: 0.0%.

How to fix or mitigate CVE-2026-34214?

Within 24 hours: inventory all Trino deployments using Iceberg connectors and identify which systems expose /ui/api/query/ or /v1/query/ endpoints. Within 7 days: immediately rotate all AWS S3 access credentials (static and temporary) used by Trino Iceberg connectors; implement network-level access restrictions to query endpoints (restrict to trusted administrative networks only). Within 30 days: upgrade to a patched Trino release when available from the vendor; evaluate migration to alternative catalog solutions or credential management approaches that do not leak credentials through API responses.

CVE-2026-34214

EUVD-2026-17459 MEDIUM

Improper Removal of Sensitive Information Before Storage or Transfer (CWE-212)

2026-03-29 https://github.com/trinodb/trino

GHSA-x27p-5f68-m644

Information Disclosure

6.5

CVSS 3.1 · NVD

Severity by source

NVD PRIMARY

6.5 MEDIUM

AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

None

Availability

None

Lifecycle Timeline

Severity Changed

Jul 24, 2026 - 21:22 NVD

HIGH MEDIUM

CVSS changed

Jul 24, 2026 - 21:22 NVD

7.7 (HIGH) 6.5 (MEDIUM)

Patch released

Mar 31, 2026 - 21:13 nvd

Patch available

EUVD ID Assigned

Mar 29, 2026 - 15:30 euvd

EUVD-2026-17459

Analysis Generated

Mar 29, 2026 - 15:30 vuln.today

CVE Published

Mar 29, 2026 - 15:13 nvd

HIGH 7.7

Blast Radius

ecosystem impact

† from your stack dependencies † transitive graph · vuln.today resolves 4-path depth

1 maven packages depend on io.trino:trino-iceberg (1 direct, 0 indirect)

Ecosystem-wide dependent count for version 439.

DescriptionNVD

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/«query_id» and /v1/query/«query_id» 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 configured to use REST Catalog with static or vended credentials can retrieve those credentials.

Impact

Anyone using Iceberg REST catalog with static or vended credentials is impacted. The credentials should be considered compromised. Vended credentials are temporary in nature so they do not need to be rotated. However, underlying data could have been exposed.

AnalysisAI

Trino's Iceberg connector leaks AWS S3 access credentials through query JSON endpoints, allowing authenticated users with write privileges to extract static or temporary credentials used for object storage access. The vulnerability exposes credentials via the query visualization API (/ui/api/query/ and /v1/query/ endpoints) when users perform write or table maintenance operations. With a CVSS of 7.7 and EPSS data not provided, this represents a confirmed credential exposure issue requiring immediate attention for organizations using Iceberg REST catalog configurations with storage credentials. No public exploit identified at time of analysis, though exploitation requires only low-privilege authenticated access.

Technical ContextAI

Trino is a distributed SQL query engine that integrates with Apache Iceberg tables via REST catalog connections. The affected component (pkg:maven/io.trino:trino-iceberg) implements table write operations and maintenance procedures that require object storage access, typically to AWS S3 or compatible storage. The vulnerability stems from CWE-212 (Improper Removal of Sensitive Information Before Storage or Transfer), where storage credentials-either static access keys or AWS STS vended (temporary) credentials-are serialized into query execution plans. These plans are exposed through Trino's query introspection features designed for performance troubleshooting and visualization. The query JSON objects, accessible via REST API endpoints and the web UI, contain complete credential handles embedded in IcebergTableExecuteHandle or similar structures, making them readable to any user who submitted a query involving write operations.

RemediationAI

Vendor-released patch: version 480. Organizations should immediately upgrade to Trino 480 or later, available at https://github.com/trinodb/trino/releases/tag/480. For deployments using static credentials, immediately rotate all AWS access keys or equivalent storage credentials that may have been exposed through query JSON endpoints, as these should be considered compromised per vendor guidance. Review access logs for the /ui/api/query/ and /v1/query/ API endpoints to identify potential unauthorized credential access. For vended credentials, while rotation is unnecessary due to their temporary nature, conduct forensic analysis of object storage access logs to determine if data was accessed outside normal operational patterns during the credential validity window. As a longer-term architectural improvement, consider migrating to IAM role-based authentication mechanisms that eliminate credential embedding in query plans. Implement network segmentation to restrict access to Trino API endpoints to authorized networks only.