CVE-2026-34214: Trino Information Disclosure Vulnerability

CVE-2026-34214 Overview

Trino, a distributed SQL query engine for big data analytics, contains a sensitive data exposure vulnerability in its Iceberg connector REST catalog implementation. From version 439 to before version 480, REST catalog static credentials (access key) or vended credentials (temporary access key) are accessible to users that have write privilege on SQL level. This allows authenticated users with limited write permissions to escalate their access by obtaining credentials that should be protected.

Critical Impact

Authenticated users with SQL-level write privileges can access sensitive REST catalog credentials, potentially leading to unauthorized access to backend data stores and cloud resources.

Affected Products

• Trino versions 439 to 479
• Trino Iceberg connector with REST catalog configuration
• Deployments using static credentials or vended credentials for Iceberg REST catalog

Discovery Timeline

• March 31, 2026 - CVE-2026-34214 published to NVD
• April 1, 2026 - Last updated in NVD database

Technical Details for CVE-2026-34214

Vulnerability Analysis

This vulnerability represents an information disclosure flaw classified under CWE-212 (Improper Removal of Sensitive Information Before Storage or Transfer). The Trino Iceberg connector fails to properly isolate REST catalog credentials from users who possess SQL-level write privileges. When interacting with Iceberg tables through the REST catalog interface, credential information is improperly exposed through the query execution path.

The vulnerability affects two credential types: static access keys (long-lived credentials configured for the REST catalog) and vended credentials (temporary access keys obtained through credential vending mechanisms). Both credential types, when exposed, could grant attackers access to the underlying storage systems such as Amazon S3, Azure Blob Storage, or Google Cloud Storage.

Root Cause

The root cause is improper credential isolation in the Trino Iceberg connector's REST catalog implementation. The system fails to adequately separate sensitive credential data from the query execution context that is accessible to users with write privileges. This represents a violation of the principle of least privilege, where users should only have access to the minimum information necessary to perform their authorized operations.

Attack Vector

The attack requires network access and low-privilege authentication with SQL-level write permissions on Trino. An attacker with these minimal privileges can exploit the vulnerability to extract REST catalog credentials without any user interaction. The scope is changed, meaning the vulnerability impacts resources beyond the vulnerable component itself—specifically, the backend storage systems authenticated by the exposed credentials.

An attacker could leverage this vulnerability to:

1. Authenticate to Trino with a user account that has write privileges on any table using the Iceberg connector with REST catalog
2. Execute specifically crafted queries or operations that trigger credential exposure
3. Capture the exposed static or vended credentials
4. Use those credentials to directly access backend storage, bypassing Trino's access controls entirely

Detection Methods for CVE-2026-34214

Indicators of Compromise

• Unusual query patterns targeting Iceberg tables from users with write privileges
• Unexpected access to backend storage systems (S3, Azure Blob, GCS) using credentials associated with Trino REST catalog
• Credential usage from IP addresses or locations inconsistent with normal Trino cluster operations
• Audit logs showing credential access or metadata operations outside normal application behavior

Detection Strategies

• Monitor Trino query logs for suspicious patterns involving Iceberg connector operations
• Implement cloud provider credential usage monitoring (AWS CloudTrail, Azure Activity Logs, GCP Audit Logs) to detect unusual credential usage patterns
• Review user privilege assignments to identify accounts with write privileges that may be at risk
• Deploy anomaly detection for storage access patterns that deviate from expected Trino cluster behavior

Monitoring Recommendations

• Enable comprehensive audit logging in Trino to track all Iceberg connector operations
• Configure alerts for credential usage outside the Trino cluster's expected network boundaries
• Implement real-time monitoring for backend storage access using the affected credentials
• Review access logs periodically for any signs of credential misuse or lateral movement

How to Mitigate CVE-2026-34214

Immediate Actions Required

• Upgrade Trino to version 480 or later immediately
• Review and rotate all REST catalog credentials (both static and vended) that may have been exposed
• Audit user accounts with SQL-level write privileges to assess potential exposure
• Review cloud provider logs for any unauthorized access using Trino catalog credentials

Patch Information

Trino has released version 480 which patches this vulnerability. Organizations should upgrade to this version or later as soon as possible. The fix addresses the improper credential exposure by properly isolating sensitive credential information from the query execution context accessible to users with write privileges.

For detailed patch information, refer to the Trino Release 480 release notes and the GitHub Security Advisory GHSA-x27p-5f68-m644.

Workarounds

• Restrict SQL-level write privileges to only essential users until patching is complete
• Consider temporarily disabling Iceberg connector REST catalog functionality if not critical to operations
• Implement network segmentation to limit access to Trino clusters from untrusted networks
• Use short-lived vended credentials with minimal permissions where possible to reduce exposure window

# Verify current Trino version
./trino --version

# After upgrading to version 480 or later, rotate credentials
# Example: Rotate AWS credentials used for REST catalog
aws iam create-access-key --user-name trino-iceberg-catalog
aws iam delete-access-key --user-name trino-iceberg-catalog --access-key-id OLD_ACCESS_KEY_ID