No advisories yet.
Solution
No solution given by the vendor.
Workaround
No workaround given by the vendor.
Thu, 26 Feb 2026 16:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| CPEs | cpe:2.3:a:traccar:traccar:*:*:*:*:*:*:*:* |
Wed, 25 Feb 2026 16:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Tue, 24 Feb 2026 10:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Traccar
Traccar traccar |
|
| Vendors & Products |
Traccar
Traccar traccar |
Mon, 23 Feb 2026 21:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Versions of the Traccar open-source GPS tracking system up to and including 6.11.1 contain an issue in which authenticated users can steal OAuth 2.0 authorization codes by exploiting an open redirect vulnerability in two OIDC-related endpoints. The `redirect_uri` parameter is not validated against a whitelist, allowing attackers to redirect authorization codes to attacker-controlled URLs, enabling account takeover on any OAuth-integrated application. As of time of publication, it is unclear whether a fix is available. | |
| Title | Traccar Vulnerable to Authorization Code Theft via Open Redirect in OIDC Provider Endpoints | |
| Weaknesses | CWE-352 CWE-601 |
|
| References |
| |
| Metrics |
cvssV3_1
|
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2026-02-25T15:20:54.780Z
Reserved: 2026-02-04T05:15:41.792Z
Link: CVE-2026-25649
Updated: 2026-02-25T15:20:46.844Z
Status : Analyzed
Published: 2026-02-23T22:16:24.927
Modified: 2026-02-26T16:23:23.333
Link: CVE-2026-25649
No data.
OpenCVE Enrichment
Updated: 2026-02-24T09:54:47Z