OwnTracks Recorder before version 1.0.5 has a critical format string vulnerability: an unauthenticated attacker can store a malicious tid value and then use it to leak memory addresses, write to memory and execute code.
What Is It
CVE-2026-131852 is a format string vulnerability (CWE-134) in json_response() and related output functions in OwnTracks Recorder. An attacker publishes a location through POST /pub or over MQTT with printf format specifiers in the tid field. Recorder stores that value. When the attacker reads it back through GET /api/0/last, the unsanitized specifiers are processed. That lets the attacker leak addresses, write to memory and ultimately execute code.
VulnCheck reported the issue. The NVD record was published on November 18, 2026, and currently has the status "Received."
Why It Matters
VulnCheck rates the flaw 9.8 (Critical) under CVSS 3.1 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) and 9.3 (Critical) under CVSS 4.0. It can be exploited over the network with low complexity. It needs no privileges and no user interaction, and confidentiality, integrity and availability impact are all High.
CISA's SSVC assessment lists exploitation as none, automatable as yes and technical impact as total. The vulnerability is not in the CISA Known Exploited Vulnerabilities (KEV) catalog, and the supplied data shows no confirmed active exploitation. Still, an unauthenticated, automatable flaw that leads to code execution should be patched quickly. This is especially true for Recorder instances that expose their HTTP or MQTT interfaces to untrusted networks.
What's Vulnerable
- Vendor: OwnTracks
- Product: Recorder
- Affected versions: all versions before 1.0.5 (semver
0through<1.0.5) - Affected functions:
json_response()and related output functions. The vulnerable code is inhttp.cin the 1.0.4 tag. - Attack surface: the
POST /puband MQTT location publishing paths (to inject the payload) andGET /api/0/last(to trigger it)
Patch Status
The issue is fixed in OwnTracks Recorder 1.0.5. The fix is in upstream commit 64a86050 and pull request #589. Upgrade to 1.0.5 or later. CISA has issued no KEV required action or remediation due date, because the CVE is not in the KEV catalog.