Bearer token exposure via query parameter acceptance
Published Sep 14, 2026 · Updated Sep 14, 2026
Information exposure in Auth0 Symfony before 5.9.0 allows remote authenticated users to leak bearer tokens through URL query parameters. The Authorizer security authenticator's authenticate() and supports() paths accept access_token query values for protected routes instead of requiring the Authorization header. A valid bearer token must reach such a route; intermediary logs, browser history, or referrer data can retain the token for replay against protected API endpoints.
Summary
What happened
Information exposure in Auth0 Symfony before 5.9.0 allows remote authenticated users to leak bearer tokens through URL query parameters. The Authorizer security authenticator's authenticate() and supports() paths accept access_token query values for protected routes instead of requiring the Authorization header. A valid bearer token must reach such a route; intermediary logs, browser history, or referrer data can retain the token for replay against protected API endpoints.
The record
- CVE
- CVE-2026-50157
- Published
- Sep 14, 2026
- Updated
- Sep 14, 2026
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-200, CWE-598, T1552
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 14, 2026CVE publishedPublication date reported by the CVE source.
- Sep 14, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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