# CVE-2025-61666: Traccar Unauthenticated Local File Inclusion on Windows - Leakage of Traccar Config File

> Unauthenticated attackers can read arbitrary files, including configuration files with passwords, on Windows installations of Traccar.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:L/SI:L/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Oct 2025
- **Updated:** 3 Oct 2025
- **Also known as:** GHSA-hprc-rph8-fj87

## What is CVE-2025-61666?

CVE-2025-61666 is a high-severity path traversal vulnerability in traccar, published on 2 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Traccar is an open source GPS tracking system. Default installs of Traccar on Windows between versions 6.1-  6.8.1 and non default installs between versions 5.8 - 6.0 are vulnerable to unauthenticated local file inclusion attacks which can lead to leakage of passwords or any file on the file system including the Traccar configuration file. Versions 5.8 - 6.0 are only vulnerable if <entry key='web.override'>./override</entry> is set in the configuration file. Versions 6.1 - 6.8.1 are vulnerable by default as the web override is enabled by default. The vulnerable code is removed in version 6.9.0.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2025-61666?


## How do I fix CVE-2025-61666?

No fix has been published for CVE-2025-61666 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-61666 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-61666 exists.

Public exploit code:

- Traccar(Windows) 6.1- 6.8.1 - Local File Inclusion (nuclei): http/cves/2025/CVE-2025-61666.yaml

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-61666 and fix it if it is affected.

What it is: CVE-2025-61666 is a high-severity path traversal vulnerability in traccar, published on 2 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-61666 exists.

Affected product: traccar. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-61666/ (Markdown: https://insights.sbomify.com/CVE-2025-61666/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-61666
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-61666
- OSV: https://osv.dev/vulnerability/CVE-2025-61666

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-61666/
Summaries are generated and may contain mistakes; the official description above is the record.