# CVE-2026-131852: OwnTracks Recorder before 1.0.5 Format String via Stored tid Value


- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 17 Nov 2026
- **Updated:** 18 Nov 2026
- **Also known as:** GHSA-4ghv-x7hp-87pc

## What is CVE-2026-131852?

CVE-2026-131852 is a critical vulnerability in OwnTracks Recorder, published on 17 Nov 2026. 

### Official description

OwnTracks Recorder before 1.0.5 contains a format string vulnerability in json_response() and related output functions that allows unauthenticated attackers to execute code by storing a malicious tid value. Attackers can publish locations via POST /pub or MQTT with printf specifiers in tid, then read them back through GET /api/0/last to leak addresses and write memory.

Weakness: CWE-134 (Use of Externally-Controlled Format String)

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

1 open source package ship an affected version, including owntracks/recorder.


| Package | Ecosystem | PURL | Affected | Fixed in |
| --- | --- | --- | --- | --- |
| `owntracks/recorder` | GitHub | `pkg:github/owntracks/recorder` | All versions | 1.0.5 |

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

Upgrade owntracks/recorder to 1.0.5 or later.

## Is CVE-2026-131852 being exploited?

There is no known exploitation of CVE-2026-131852 in the wild and no public exploit code.

Public exploit code:

- OwnTracks Recorder < 1.0.5: json_response() passes attacker JSON as the printf format of mg_printf_data — a stored location tid with %p leaks live pointers via GET /api/0/last and %n crashes the daemon (rc=139) into a storage crash-loop. Real 1.0.4 vs vendor-fixed 1.0.5 under a crash supervisor. (github_poc): https://github.com/googlesky/CVE-2026-131852

## Fix prompt for AI coding agents

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

What it is: CVE-2026-131852 is a critical vulnerability in OwnTracks Recorder, published on 17 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-131852 in the wild and no public exploit code.

Affected packages and fixed versions:
- owntracks/recorder (GitHub): affected all versions; fixed in 1.0.5

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-131852/ (Markdown: https://insights.sbomify.com/CVE-2026-131852/index.md)
```

## Sources

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

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