CVE-2026-108737

Published: Ott 11, 2026 Last Modified: Ott 11, 2026
ExploitDB:
Other exploit source:
Google Dorks:
HIGH 7,6
Attack Vector: network
Attack Complexity: low
Privileges Required: none
User Interaction: passive
Confidentiality: N/A
Integrity: N/A
Availability: N/A
MEDIUM 6,8
Attack Vector: network
Attack Complexity: high
Privileges Required: none
User Interaction: required
Scope: unchanged
Confidentiality: high
Integrity: high
Availability: none

Description

AI Translation Available

Traccar through 6.16.0 contains a weak password recovery vulnerability that allows attackers to reuse password reset tokens as session credentials because TokenManager does not bind tokens to a purpose. Attackers holding a leaked reset link can obtain a full session via /api/session or change passwords via /api/password/update, retaining access for seven days even after the victim resets their password.

640

Weak Password Recovery Mechanism for Forgotten Password

Incomplete
Common Consequences
Security Scopes Affected:
Access Control Availability Integrity Other
Potential Impacts:
Gain Privileges Or Assume Identity Dos: Resource Consumption (Other) Other
Applicable Platforms
All platforms may be affected
View CWE Details
https://github.com/traccar/traccar
https://github.com/traccar/traccar/blob/cfab560c79ee9c9eaa41c79c6df351e820d6284…
https://github.com/traccar/traccar/blob/cfab560c79ee9c9eaa41c79c6df351e820d6284…
https://github.com/traccar/traccar/blob/cfab560c79ee9c9eaa41c79c6df351e820d6284…
https://hackmd.io/@haind/traccar-token-purpose-confusion
https://www.vulncheck.com/advisories/traccar-through-6.16.0-weak-password-recov…