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.
Published: 2026-02-23
Score: 7.3 High
EPSS: < 1% Very Low
KEV: No
Impact: Unauthorized Account Takeover via Auth Code Theft
Action: Assess Impact
AI Analysis

Impact

Authenticated users of the Traccar GPS tracking system can steal OAuth 2.0 authorization codes. Two OIDC‑related endpoints fail to validate the redirect_uri parameter against a whitelist, allowing attackers to redirect the authorization code to an attacker‑controlled URL. The stolen code can then be exchanged for access tokens, enabling full takeover of any account that uses OAuth integration.

Affected Systems

The vulnerability affects all releases of the Traccar open‑source GPS tracking platform up to and including version 6.11.1. No specific patch has been published at the time of this advisory, and the CVE lists no workaround from the vendor.

Risk and Exploitability

The CVSS score of 7.3 indicates a high potential for damage, yet the EPSS score is below 1 %, suggesting that exploitation is currently unlikely. The advisory is not listed in CISA’s KEV catalog. Attackers would exploit the flaw by interacting with the vulnerable OIDC endpoints over the network, supplying an arbitrary redirect_uri. Successful exploitation results in the attacker gaining the victim’s access tokens and thereby full control of the victim’s Traccar account and any downstream services that rely on OAuth authentication.

Generated by OpenCVE AI on April 17, 2026 at 16:12 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • If your Traccar deployment uses OAuth 2.0, immediately suspend or disable OIDC endpoints until an official patch is available.
  • Configure the server to allow only trusted redirect_uri values by implementing a strict whitelist for OIDC redirect endpoints.
  • Apply any Traccar update that addresses the flaw as soon as it becomes available.

Generated by OpenCVE AI on April 17, 2026 at 16:12 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

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

{'options': {'Automatable': 'no', 'Exploitation': 'poc', 'Technical Impact': 'total'}, 'version': '2.0.3'}


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

{'score': 7.3, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:N'}


cve-icon MITRE

Status: PUBLISHED

Assigner: GitHub_M

Published:

Updated: 2026-02-25T15:20:54.780Z

Reserved: 2026-02-04T05:15:41.792Z

Link: CVE-2026-25649

cve-icon Vulnrichment

Updated: 2026-02-25T15:20:46.844Z

cve-icon NVD

Status : Analyzed

Published: 2026-02-23T22:16:24.927

Modified: 2026-02-26T16:23:23.333

Link: CVE-2026-25649

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-04-17T16:15:22Z

Weaknesses