CVE-2026-131852
9.8CriticalPublished 18 Nov 2026 · NVD status: Received · AI triage by gemini-3.1-flash-lite
Critical
0CVSS v3.110
- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User action
- None
- Impact
- Full C/I/A compromise
- Weakness
- CWE-134
What an attacker gets
Unauthenticated attackers can execute arbitrary code or leak memory by sending malicious location data. They only need network access to the OwnTracks Recorder API or MQTT broker to trigger the vulnerability.
Root cause
The json_response function uses user-supplied tid values directly as format strings in output functions.
Affected versions
OwnTracks Recorder before 1.0.5
CVSS v3.1 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Fix & remediation
Upgrade to OwnTracks Recorder 1.0.5 or later. If you cannot patch immediately, restrict network access to the API and MQTT endpoints to trusted sources only.
AI-suggested. Run it in staging first and check it against the vendor advisory. Why?
NVD 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.
References
- https://github.com/owntracks/recorder/blob/1.0.4/http.c#L369-L410
- https://github.com/owntracks/recorder/commit/64a86050a1ac6cb5f704e296ec9182f750d143c8
- https://github.com/owntracks/recorder/pull/589
- https://github.com/owntracks/recorder/releases/tag/1.0.5
- https://www.vulncheck.com/advisories/owntracks-recorder-before-1.0.5-format-string-via-stored-tid-value