CVE-2026-16336 trinodb CVE debrief

Who should care

Defenders responsible for trinodb trino deployments should assess the potential impact of open redirect attacks on their systems and verify the affected versions and configurations in their environment.

Why it matters

The CVE-2026-16336 vulnerability in trinodb trino 481 allows for open redirect attacks, which can have significant consequences for defenders. The vulnerability can be exploited remotely, and verification of affected versions and configurations is necessary to determine the scope of the vulnerability.

• Open redirect attacks can lead to phishing attacks or unauthorized access to sensitive information
• The vulnerability can be exploited remotely, increasing the attack surface
• Verification of affected versions and configurations is necessary to determine the scope of the vulnerability

Technical summary

The vulnerability is caused by a manipulation of the redirect_uri argument in the ExternalUriInfo.java file of the OAuth2/OIDC component in trinodb trino 481. This allows for an open redirect attack, which can be initiated remotely. The attack can lead to phishing attacks or unauthorized access to sensitive information. Defenders should prioritize verifying the affected versions and configurations of trinodb trino in their environment and assess the potential impact of open redirect attacks on their systems. The CVE record and NVD entry provide information about the vulnerability, but the vendor has not responded to the issue report yet.

Defensive priority

Defenders should prioritize verifying the affected versions and configurations of trinodb trino in their environment, and assess the potential impact of open redirect attacks on their systems.

Recommended defensive actions

• Verify the affected versions and configurations of trinodb trino in your environment.
• Assess the potential impact of open redirect attacks on your systems.
• Implement compensating controls to mitigate the vulnerability.
• Review relevant monitoring, detection, and logs for exposed assets that need extra review.
• Track exceptions, retest remediated assets, and close the item only after evidence is documented.
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up.
• Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed.

Evidence notes

The CVE record and NVD entry provide information about the vulnerability, but the vendor has not responded to the issue report yet. The open redirect vulnerability is related to the OAuth2/OIDC component of trinodb trino.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.