CVE
Traccar 3.15 before 6.17.0 Authentication Bypass via Empty LDAP Password
Affects Traccar 3.15 through 6.16.x when LDAP authentication is enabled against a directory that permits unauthenticated binds. Fixed in 6.17.0.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 6.17.0
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 6.17.0.
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 26/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Unclear
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Traccar, a GPS tracking application, has an authentication bypass when LDAP login is enabled: it accepts empty passwords and performs unauthenticated LDAP binds. A remote attacker who knows a valid username can log in without a password and obtain a session for any account, including administrators.
Read the original 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.
Who should check
Teams running Traccar 3.15 through 6.16.x with LDAP authentication enabled against a directory that permits unauthenticated binds
Read the source excerpt
“causing LDAP binds to be performed as unauthenticated binds when LDAP authentication is enabled”
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure17/25No login or user action needed, reachable over the network without a login · Unknown: Advisories don't say whether default setups are affected
- Reach?/20Unknown. No tracked technology or package matched
- Severity9.1/10CVSS 9.1
- No patch0/5No signal
What would change the score
- Would score about 71 if added to CISA KEV
- Would score about 66 if CISA's SSVC rates exploitation active
- Would score about 31 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 6.17.0.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-126777 (Traccar 3.15 before 6.17.0 Authentication Bypass via Empty LDAP Password), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-126777 (entry last updated 2026-11-11):
Affected:
- Traccar Traccar: from 3.15, fixed in 6.17.0
Fixed versions: 6.17.0.
Conditions (all must be true for the bug to be hit):
- Traccar versions 3.15 through 6.16.x (fixed in 6.17.0) (source: https://www.vulncheck.com/advisories/traccar-3.15-before-6.17.0-authentication-bypass-via-empty-ldap-password)
- LDAP authentication is enabled (source: https://www.vulncheck.com/advisories/traccar-3.15-before-6.17.0-authentication-bypass-via-empty-ldap-password)
- The LDAP directory permits unauthenticated binds (source: https://www.vulncheck.com/advisories/traccar-3.15-before-6.17.0-authentication-bypass-via-empty-ldap-password)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-126777 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-126777 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/traccar/traccar/commit/552c31f2097dbed9edef7cfe174c50b16febdc21
- https://github.com/traccar/traccar/releases/tag/v6.17.0
- https://github.com/traccar/traccar/blob/v6.16.0/src/main/java/org/traccar/database/LdapProvider.java#L171-L176
- https://github.com/traccar/traccar/blob/v3.15/src/org/traccar/database/LdapProvider.java#L163-L169
- https://www.vulncheck.com/advisories/traccar-3.15-before-6.17.0-authentication-bypass-via-empty-ldap-password
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-126777
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-126777"}.Timeline
- CVE published
- First seen by cve.now
- Posted on X by cve.now
Affected versions
- Traccar Traccar
From 3.15 · fixed in 6.17.0
Evidence 7
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Other links · 5
- Patch
- Repository
- Repository
- Repository
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-126777
Is CVE-2026-126777 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
A login with an empty password is accepted when LDAP authentication is used, which gives a session for any account, including administrator accounts.Source: vulncheck.com
Which versions are affected by CVE-2026-126777?
Traccar: from 3.15 before 6.17.0.Source: cve.now feed data
Am I affected, and how do I check?
Traccar versions 3.15 through 6.16.x are in the affected range, but only where LDAP authentication is enabled and the LDAP directory permits unauthenticated binds. To check, look at the Traccar version and whether LDAP authentication is enabled in the server configuration, then confirm with the directory administrator whether unauthenticated binds are permitted.Source: vulncheck.com
How do I fix CVE-2026-126777?
Upgrade Traccar to 6.17.0 or later, which is the fixed version listed for this issue.Source: vulncheck.com