CVE-2026-25649
Open Redirect in Traccar OIDC Enables OAuth Code Theft
Publication date: 2026-02-23
Last updated on: 2026-02-26
Assigner: GitHub, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| traccar | traccar | to 6.11.1 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-601 | The web application accepts a user-controlled input that specifies a link to an external site, and uses that link in a redirect. |
| CWE-352 | The web application does not, or cannot, sufficiently verify whether a request was intentionally provided by the user who sent the request, which could have originated from an unauthorized actor. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability affects versions of the Traccar open-source GPS tracking system up to and including 6.11.1. It involves an open redirect issue in two OpenID Connect (OIDC)-related endpoints where the `redirect_uri` parameter is not validated against a whitelist. Authenticated users can exploit this flaw to steal OAuth 2.0 authorization codes by redirecting them to attacker-controlled URLs.
By stealing these authorization codes, attackers can potentially take over accounts on any OAuth-integrated application that relies on Traccar for authentication.
How can this vulnerability impact me? :
The vulnerability can lead to account takeover on OAuth-integrated applications. Attackers who exploit the open redirect flaw can steal authorization codes and use them to gain unauthorized access to user accounts.
This can result in unauthorized access to sensitive location data tracked by the Traccar system or any other linked services, potentially compromising user privacy and security.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
I don't know
What immediate steps should I take to mitigate this vulnerability?
I don't know