{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-25649 exists.","fix":"No fix has been published for CVE-2026-25649 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-25649 is a high-severity vulnerability in traccar, published on 23 Feb 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-25649 and fix it if it is affected.\n\nWhat it is: CVE-2026-25649 is a high-severity vulnerability in traccar, published on 23 Feb 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-25649 exists.\n\nAffected product: traccar. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-25649/ (Markdown: https://insights.sbomify.com/CVE-2026-25649/index.md)","id":"CVE-2026-25649","markdown":"https://insights.sbomify.com/CVE-2026-25649/index.md","name":"CVE-2026-25649","record":{"aliases":["GHSA-ccc7-4r59-4pp7"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"GPS tracking system","requires_auth":"low_privilege","summary":"Attackers can steal OAuth authorization codes via open redirect in OIDC endpoints, leading to account takeover in integrated applications.","user_interaction":"required","vuln_class":"open_redirect"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"traccar","vendor":"traccar"}],"cvss":{"score":7.3,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-601","name":"URL Redirection to Untrusted Site"},{"id":"CWE-352","name":"Cross-Site Request Forgery"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"Traccar Vulnerable to Authorization Code Theft via Open Redirect in OIDC Provider Endpoints","id":"CVE-2026-25649","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"open_redirect","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"MCP Salesforce Connector has arbitrary attribute access which leads to disclosure of Salesforce auth token","id":"CVE-2026-25650"},"packages":[],"prev":{"headline":"Traccar Vulnerable to Stored Cross-Site Scripting (XSS) via Malicious SVG File Upload","id":"CVE-2026-25648"},"products":["traccar"],"published":"2026-02-23","related":[{"cvss_score":9.7,"headline":"Traccar's unrestricted file upload vulnerability in device image upload could lead to remote code execution","id":"CVE-2024-31214","kev_date_added":null,"published":"2024-04-10"},{"cvss_score":9.5,"headline":"Use of default credentials at Traccar fleet management solution","id":"CVE-2024-7746","kev_date_added":null,"published":"2024-08-13"},{"cvss_score":8.7,"headline":"Traccar Vulnerable to Stored Cross-Site Scripting (XSS) via Malicious SVG File Upload","id":"CVE-2026-25648","kev_date_added":null,"published":"2026-02-23"},{"cvss_score":8.5,"headline":"An unrestricted file upload vulnerability in traccar leads to RCE","id":"CVE-2023-50729","kev_date_added":null,"published":"2024-01-15"},{"cvss_score":7.7,"headline":"LDAP injection vulnerability in Traccar GPS Tracking System","id":"CVE-2020-5246","kev_date_added":null,"published":"2020-07-14"},{"cvss_score":7.1,"headline":"Traccar Missing Origin Validation in WebSockets","id":"CVE-2025-68930","kev_date_added":null,"published":"2026-02-23"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-02-25","vendors":["traccar"]},"summary":"Attackers can steal OAuth authorization codes via open redirect in OIDC endpoints, leading to account takeover in integrated applications.","url":"https://insights.sbomify.com/CVE-2026-25649/"}