Quick answers
- Is CVE-2026-104203 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-104203 being exploited in the wild.
- How severe is CVE-2026-104203?
- High severity, with a CVSS score of 7.5, published 4 November 2026.
- Which products and versions are affected?
- Traccar 5.1 through 6.14.x.
- Is there a fix for CVE-2026-104203?
- Yes: fixed in 6.15.0. Until then: Reverse proxies that reject or rewrite semicolon path parameters may block this attack vector prior to upgrade. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-104203 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-104203?
- Check whether you run Traccar at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: 6.15.0
Reverse proxies that reject or rewrite semicolon path parameters may block this attack vector prior to upgrade.
Technical details
The vulnerability exists in versions 5.1 through 6.14.x where WebModule's Guice filter mapping and WebServer's Jetty ResourceServlet interpret path parameters differently. An attacker can craft a request to /api/media/* with a semicolon to bypass MediaFilter's session and device authorization checks while still being routed by Jetty to the ResourceServlet, which serves the requested file. The attack requires knowledge of a valid device ID and media filename but no authentication.
Affected products
- Traccar Traccar 5.1 through 6.14.x
Timeline
- 2026-11-04: disclosed