CVE-2026-104203 · Package
NO FIX YET · SEE WHAT TO DO
Traccar GPS tracking server versions 5.1 through 6.14.x let an unauthenticated attacker bypass media access checks by inserting a semicolon into the /api/media path. The attacker can then download protected uploaded media such as photos, audio or video if they know or guess a device unique ID and media filename.
first public Oct 17, 2026 · 1 source
Check it with your coding agent
It checks your repository and tells you if you’re affected, with the fix.
Teams running self-hosted Traccar from 5.1 through 6.14.x where media uploads are stored and the /api/media endpoint is reachable from the network. Deployments behind a reverse proxy that rejects or rewrites semicolon path parameters may be blocked, and managed hosting handled by a vendor is outside the team's control.
Not affected if managed-hosting, no-media-uploads, proxy-blocks-semicolons
Who cares gps-tracking, java, self-hosted, traccar
5.1 and 6.14.x./api/media/ routes reachable from the internet, and check whether a reverse proxy blocks or rewrites semicolon path parameters.6.15.0.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.
Are you affected?
Tell InfraStack what you run. It checks this one, and every next one, against your stack.
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.