Authorization-code disclosure via unvalidated callback URI
Published Jul 21, 2026 · Updated Jul 21, 2026
Open redirect in Trino 481 OAuth2/OIDC authentication allows remote attackers to redirect authorization codes via request context. ExternalUriInfo and the OAuth challenge handlers build the callback URI from the request base URI and forwarded-prefix data without pinning it to a canonical origin. Exploitation requires OAuth2 to be enabled, a victim to complete login, and the identity provider to accept a loosely matched callback, exposing the authorization code.
Summary
What happened
Open redirect in Trino 481 OAuth2/OIDC authentication allows remote attackers to redirect authorization codes via request context. ExternalUriInfo and the OAuth challenge handlers build the callback URI from the request base URI and forwarded-prefix data without pinning it to a canonical origin. Exploitation requires OAuth2 to be enabled, a victim to complete login, and the identity provider to accept a loosely matched callback, exposing the authorization code.
The record
- CVE
- CVE-2026-16336
- Published
- Jul 21, 2026
- Updated
- Jul 21, 2026
- Vendor
- Trino Software Foundation
- Product
- Trino
- Classifications
- CWE-601, T1528
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 21, 2026CVE publishedPublication date reported by the CVE source.
- Jul 21, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=481
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo