CVE-2026-34214: 
Java vulnerability analysis and mitigation

CVE-2026-34214 is a credential exposure vulnerability in Trino's Iceberg connector REST catalog that allows authenticated users with SQL write privileges to access static or vended object storage credentials via query JSON. It affects Trino versions 439 through 479 (i.e., >= 439, < 480) and was published on March 27, 2026, with a patch released in version 480. The vulnerability carries a CVSS v3.1 base score of 7.7 (High) per the GitHub Advisory, with a changed scope reflecting that exposed credentials can impact resources beyond the Trino system itself (Github Advisory, Trino Advisory).

The root cause is classified under CWE-212 (Improper Removal of Sensitive Information Before Storage or Transfer) and CWE-312 (Cleartext Storage of Sensitive Information). Trino's Query JSON feature — a query visualization and performance troubleshooting facility — serializes the full query plan including table write handles and table procedure handles. When the Iceberg connector is configured to use a REST catalog with static credentials (e.g., AWS S3 access keys) or vended credentials (temporary access keys), those credentials are embedded in cleartext within the serialized query JSON. Any user who submits a write or table maintenance query can then retrieve their own query JSON via the /ui/api/query/«query_id» or /v1/query/«query_id» endpoints and extract the embedded storage credentials (Github Advisory, Trino Advisory).

Successful exploitation allows an authenticated user with SQL write access to retrieve object storage credentials (such as AWS S3 access keys) that may grant access to underlying data stores beyond the scope of Trino itself. Static credentials should be considered fully compromised and must be rotated immediately, while vended (temporary) credentials are time-limited but may have already exposed underlying data during their validity window. There is no integrity or availability impact, but the confidentiality breach extends to all data accessible via the exposed credentials, potentially enabling lateral movement to cloud storage resources (Github Advisory, Trino Advisory).

1. Obtain write access: Authenticate to a Trino instance (versions 439–479) with an account that has SQL write privileges on a table backed by the Iceberg connector configured with a REST catalog using static or vended credentials.
2. Trigger a write or maintenance operation: Execute a write query (e.g., INSERT INTO, DELETE FROM) or a table maintenance procedure (e.g., ALTER TABLE ... EXECUTE optimize) against the target Iceberg table to generate a query with embedded storage credential handles.
3. Retrieve the query ID: Note the query ID returned by Trino upon query submission, or locate it via the Trino UI.
4. Fetch query JSON: Send an HTTP GET request to /ui/api/query/«query_id» or /v1/query/«query_id» on the Trino coordinator to retrieve the full serialized query JSON.
5. Extract credentials: Parse the query JSON response to locate the serialized table write handles or procedure handles, which contain the plaintext static access key or temporary vended credentials for the configured object storage (e.g., AWS S3) (Github Advisory, Trino Advisory).

• Network: Unusual or repeated HTTP GET requests to /ui/api/query/«query_id» or /v1/query/«query_id» endpoints on the Trino coordinator, especially from users who do not typically access query JSON programmatically.
• Logs: Trino access logs showing a pattern of a user submitting a write query immediately followed by fetching the corresponding query JSON via the API; access to query JSON for queries belonging to other users (if access controls are misconfigured).
• Cloud/Storage: Unexpected API calls to object storage (e.g., AWS S3, GCS) using credentials associated with the Iceberg REST catalog configuration, originating from IP addresses not associated with the Trino cluster — indicating potential credential theft and misuse (Trino Advisory).

Upgrade Trino to version 480 or later, which contains the fix that prevents storage credentials from being serialized into query JSON (Trino Release 480). Organizations using static credentials with the Iceberg REST catalog on affected versions (439–479) should immediately rotate those credentials, as they must be considered compromised. Vended (temporary) credentials do not require rotation but any data accessible via those credentials during their validity window should be reviewed for unauthorized access. As an interim measure, restrict access to the /ui/api/query/ and /v1/query/ endpoints to trusted users only (Github Advisory, Trino Advisory).

The vulnerability was disclosed by researcher findinpath and coordinated by findepi, with remediation contributed by Trino developers ebyhr, chenjian2664, and losipiuk. The advisory was published on March 27, 2026, and received standard community tracking across vulnerability databases and aggregators. No significant media coverage or notable public researcher commentary beyond the advisory itself has been identified (Trino Advisory).