# CVE-2026-44314: Traccar: Missing edit authorization on device image upload allows read-only users to write files

> Read-only users can upload and replace device images due to missing edit authorization checks in the image upload endpoint.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 May 2026
- **Updated:** 26 May 2026
- **Also known as:** GHSA-33v4-5x2g-7mjm

## What is CVE-2026-44314?

CVE-2026-44314 is a medium-severity missing authorization vulnerability in traccar, published on 26 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Traccar is an open source GPS tracking system. Prior to 6.13.0, DeviceResource.uploadImage authorizes the target device only through Condition.Permission(User.class, getUserId(), Device.class) and then immediately streams the uploaded body into mediaManager.createFileStream(...). Unlike the generic mutation path in BaseObjectResource.update and the explicit device mutation handler updateAccumulators, this route never invokes permissionsService.checkEdit(getUserId(), Device.class, false, false). The skipped guard is exactly where Traccar enforces readonly and deviceReadonly restrictions for non-admin users. An unauthorized user can replace a device’s stored image file under the server media directory. This allows modification of UI-visible device media and any downstream workflows that rely on the persisted image, despite other device update paths correctly rejecting the same identity. This vulnerability is fixed in 6.13.0.

Weakness: CWE-863 (Incorrect Authorization)

## Which versions are affected by CVE-2026-44314?

It affects 1 product.


Products: Traccar Traccar.

## How do I fix CVE-2026-44314?

No fix has been published for CVE-2026-44314 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-44314 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-44314 exists.

## Other vulnerabilities in traccar

- [CVE-2024-31214](https://insights.sbomify.com/CVE-2024-31214/): Traccar's unrestricted file upload vulnerability in device image upload could lead to remote code execution (critical 9.7)
- [CVE-2024-7746](https://insights.sbomify.com/CVE-2024-7746/): Use of default credentials at Traccar fleet management solution (critical 9.5)
- [CVE-2026-25648](https://insights.sbomify.com/CVE-2026-25648/): Traccar Vulnerable to Stored Cross-Site Scripting (XSS) via Malicious SVG File Upload (high 8.7)
- [CVE-2023-50729](https://insights.sbomify.com/CVE-2023-50729/): An unrestricted file upload vulnerability in traccar leads to RCE (high 8.5)
- [CVE-2020-5246](https://insights.sbomify.com/CVE-2020-5246/): LDAP injection vulnerability in Traccar GPS Tracking System (high 7.7)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-44314 and fix it if it is affected.

What it is: CVE-2026-44314 is a medium-severity missing authorization vulnerability in traccar, published on 26 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-44314 exists.

Affected product: traccar. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-44314/ (Markdown: https://insights.sbomify.com/CVE-2026-44314/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-44314
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-44314
- OSV: https://osv.dev/vulnerability/CVE-2026-44314

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-44314/
Summaries are generated and may contain mistakes; the official description above is the record.