# CVE-2026-126777: Traccar 3.15 before 6.17.0 Authentication Bypass via Empty LDAP Password

> Unauthenticated attackers knowing a username can log in as any Traccar account, including admins, via LDAP with an empty password.

- **Severity:** Critical 9.1 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Harmful if only installed:** No
- **Needs a specific call:** No
- **Fix available:** No
- **Published:** 11 Nov 2026
- **Updated:** 11 Nov 2026
- **Also known as:** GHSA-fjf2-ffvm-qw56

## What is CVE-2026-126777?

CVE-2026-126777 is a critical authentication bypass vulnerability in Traccar, published on 11 Nov 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Traccar 3.15 before 6.17.0 contains an authentication bypass vulnerability in LdapProvider.login() that fails to reject empty passwords, causing LDAP binds to be performed as unauthenticated binds when LDAP authentication is enabled. Unauthenticated attackers who know a valid username can log in via POST /api/session or HTTP Basic authentication with an empty password against directories that permit unauthenticated binds, obtaining sessions for any account including administrators.

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2026-126777?

Only installations with a non-default setting turned on are exposed.


## How do I fix CVE-2026-126777?

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

## Is CVE-2026-126777 being exploited?

There is no known exploitation of CVE-2026-126777 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-126777 and fix it if it is affected.

What it is: CVE-2026-126777 is a critical authentication bypass vulnerability in Traccar, published on 11 Nov 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-126777 in the wild and no public exploit code.
Exposure: Only installations with a non-default setting turned on are exposed.

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-2026-126777/ (Markdown: https://insights.sbomify.com/CVE-2026-126777/index.md)
```

## Sources

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

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