Raw vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:NCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2026-25649 is a high-severity CSRF (CWE-352) vulnerability in Traccar Traccar. Its CVSS base score is 7.3 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 4th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
The strongest mitigations our analysis identified map to SI-10 (Information Input Validation) and AC-3 (Access Enforcement) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2026-25649 is an open redirect vulnerability (CWE-601, CWE-352) in two OpenID Connect (OIDC)-related endpoints of the Traccar open-source GPS tracking system, affecting all versions up to and including 6.11.1. The flaw stems from a lack of validation for the `redirect_uri` parameter against a whitelist, enabling authenticated users to manipulate OAuth 2.0 authorization code redirects.
Authenticated attackers with low privileges can exploit this vulnerability remotely (AV:N) with low complexity (AC:L), though it requires user interaction (UI:R). By controlling the `redirect_uri`, they can steal authorization codes and redirect them to attacker-controlled URLs, achieving account takeover on any OAuth-integrated application and resulting in high confidentiality and integrity impacts (CVSS:3.1 score of 7.3; C:H/I:H/A:N/S:U).
The primary advisory, published on GitHub at https://github.com/traccar/traccar/security/advisories/GHSA-ccc7-4r59-4pp7 on 2026-02-23, describes the issue but notes that as of the time of publication, it is unclear whether a fix is available. Security practitioners should monitor for updates and consider restricting authenticated access or disabling OIDC endpoints until mitigation is confirmed.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-7482
Vulnerability Data
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…
more
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.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V3.3.2V3.5.1V10.2.1V3.7.2
Mitigating Controls (NIST 800-53 r5) AI
Input validation directly checks and rejects untrusted redirect targets before they are used in a response.
Access enforcement requires verifying that state-changing requests originate from the authenticated user rather than a forged cross-site source.
Information flow enforcement can restrict redirects to only approved/trusted destinations, stopping untrusted user-supplied URLs from being followed.
Protecting session authenticity prevents attackers from replaying or forging authenticated requests via the victim's browser.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure SDLC practices directly require anti-CSRF controls such as tokens or SameSite attributes.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
By denying access to phishing or malicious sites, the control lowers the likelihood that a user will be tricked into submitting a forged request that performs an unintended action on another site.