Skip to main content
← Vulnerabilities

Traccar: Authentication bypass via path parameters exposes protected device media

Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.

7.5HighCNA
Exploited
No known exploitation
Fix
Fixed in 6.15.0
Who is exposed
Not reported

Do first: Upgrade to a fixed version: 6.15.0.

25Pcve.now Index 25 of 100 · methodology v3 · provisional
  • Exploitation?/40Exploitation: unknown (data gap). No CISA SSVC exploitation rating yet
  • Exposure17/25No login or user action needed, reachable over the network without a login · Data gap: Advisories don't say whether default setups are affected
  • Reach?/20Reach: unknown (data gap). No tracked technology or package matched
  • Severity7.5/10CVSS 7.5
  • No patch0/5No signal

What would change the score

  • Would score about 70 if added to CISA KEV
  • Would score about 65 if CISA's SSVC rates exploitation active
  • Would score about 30 if advisories confirm default setups are exposed

CVE-2026-104203 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 7.5 (high) and affects traccar; fixed in 6.15.0.

Published
Last modified
Published
Not listed in CISA KEV
25/100 · provisional
Unclear
Fix
Fixed in 6.15.0
None on Exploit-DB, Metasploit or GitHub

Summary

Traccar, an open source GPS tracking system, has an authentication bypass in its media file handling that lets a remote attacker without logging in read protected device media files, such as photos, audio, or video, by inserting a semicolon into the request path. The bug is reached remotely over the network with no login and no user action, and it is fixed in a later release.

Read the original description

Traccar is an open source GPS tracking system. From 5.1 until 6.15.0, WebModule.java's MediaFilter Guice mapping and WebServer.java's Jetty ResourceServlet assign different routing meanings to path parameters at /api/media/*. An unauthenticated attacker who knows or guesses a device unique ID and media filename can insert a semicolon at the Servlet boundary, bypass MediaFilter's session and device authorization checks, and retrieve the protected media because Jetty still dispatches the noncanonical path to ResourceServlet. The demonstrated impact is read-only disclosure of a protected device media file; depending on the deployment and stored media, this could expose photographs, audio, video, or other uploaded files. The advisory does not establish directory listing, traversal, modification, account takeover, denial of service, or code execution. Reverse proxies that reject or rewrite semicolon path parameters may block the request. This issue is fixed in version 6.15.0.

What to do

  • Upgrade to a fixed version: 6.15.0.

  • Workaround: A path-preserving reverse proxy can reject semicolon path parameters and other non-canonical paths before forwarding requests to Traccar.

Timeline

  1. CVE published
  2. First seen by cve.now

Affected versions

  • traccar traccar

    From 5.1 · fixed in 6.15.0

Evidence 3

  1. Advisory
  2. Repository
  3. Repository

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

FAQ

Questions about CVE-2026-104203

Is CVE-2026-104203 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

Which versions are affected by CVE-2026-104203?

traccar: from 5.1 before 6.15.0.Source: cve.now feed data

How do I fix CVE-2026-104203?

Upgrade Traccar to 6.15.0 or later. As a temporary mitigation, a path-preserving reverse proxy can reject semicolon path parameters and other non-canonical paths before forwarding requests to Traccar.Source: github.com