Nixpkgs security tracker

Login with GitHub

Details of issue NIXPKGS-2026-0303

NIXPKGS-2026-0303
published on
Permalink CVE-2026-23521
6.5 MEDIUM
  • CVSS version: 3.1
  • Attack vector (AV): NETWORK
  • Attack complexity (AC): LOW
  • Privileges required (PR): LOW
  • User interaction (UI): NONE
  • Scope (S): UNCHANGED
  • Confidentiality impact (C): NONE
  • Integrity impact (I): HIGH
  • Availability impact (A): NONE
updated 2 months, 1 week ago by @mweinelt Activity log
  • Created suggestion
  • @mweinelt ignored
    7 packages
    • tests.home-assistant-component-tests.traccar_server
    • home-assistant-component-tests.traccar_server
    • tests.home-assistant-component-tests.traccar
    • home-assistant-component-tests.traccar
    • python314Packages.pytraccar
    • python313Packages.pytraccar
    • python312Packages.pytraccar
  • @mweinelt accepted
  • @mweinelt published on GitHub
Traccar vulnerable to Path Traversal and External Control of File Name or Path

Versions of the Traccar open-source GPS tracking system up to and including 6.11.1 contain an issue in which authenticated users who can create or edit devices can set a device `uniqueId` to an absolute path. When uploading a device image, Traccar uses that `uniqueId` to build the filesystem path without enforcing that the resolved path stays under the media root. This allows writing files outside the media directory. As of time of publication, it is unclear whether a fix is available.

Affected products

traccar
  • ==<= 6.11.1

Matching in nixpkgs

Ignored packages (7)

Package maintainers

https://github.com/traccar/traccar/security/advisories/GHSA-rc28-cvfc-chqr