Skip to main content
Menu
CVEs

CVE

OwnTracks Recorder remote code execution via format string in tid

OwnTracks Recorder before 1.0.5 is affected when a tid value containing printf specifiers is stored via POST /pub or MQTT. The fix is version 1.0.5.

CVE-2026-131852EUVD-2026-128328

Written by a model from the sources below. Verify against them.

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

9.3CriticalCNA
Exploited
No known exploitation
Fix
Fixed in 1.0.5
Who is exposed
Not reported

Do first: Upgrade to a fixed version: 1.0.5.

Published
Last modified
Reference
Last checked
26/100 · provisional
Unclear
None on Exploit-DB, Metasploit or GitHub

Summary

OwnTracks Recorder, before the 1.0.5 fix, has a format string flaw that lets unauthenticated attackers run code and leak or write memory. They reach it remotely, without logging in, by publishing a location with printf specifiers in the tid value over POST /pub or MQTT and then reading it back through GET /api/0/last.

Original 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.

Who should check

Teams running OwnTracks Recorder before 1.0.5 that accept location publishes via POST /pub or MQTT

“Affecting Recorder >= 0, < 1.0.5”

vulncheck.com

cve.now Index

26Pcve.now Index 26 of 100 · methodology v3 · provisional
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure17/25No login or user action needed, reachable over the network without a login · Unknown: Advisories don't say whether default setups are affected
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity9.3/10CVSS 9.3
  • No patch0/5No signal

What would change the score

  • Would score about 71 if added to CISA KEV
  • Would score about 66 if CISA's SSVC rates exploitation active
  • Would score about 31 if advisories confirm default setups are exposed

What to do

  • Upgrade to a fixed version: 1.0.5.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-131852 (OwnTracks Recorder before 1.0.5 Format String via Stored tid Value), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-131852 (entry last updated 2026-11-17):
Affected:
- OwnTracks Recorder: fixed in 1.0.5
Fixed versions: 1.0.5.
Conditions (all must be true for the bug to be hit):
- OwnTracks Recorder before 1.0.5 (source: https://www.vulncheck.com/advisories/owntracks-recorder-before-1.0.5-format-string-via-stored-tid-value)
- Attacker stores a tid value containing printf specifiers, published via POST /pub or MQTT, which is later read back via GET /api/0/last (source: https://www.vulncheck.com/advisories/owntracks-recorder-before-1.0.5-format-string-via-stored-tid-value)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-131852 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-131852 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- 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://github.com/owntracks/recorder/blob/1.0.4/http.c#L369-L410
- https://www.vulncheck.com/advisories/owntracks-recorder-before-1.0.5-format-string-via-stored-tid-value
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-131852
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-131852"}.

Timeline

  1. CVE published1 day
  2. First seen by cve.now

Affected versions

  • OwnTracks Recorder

    fixed in 1.0.5

Evidence 7

CVE record · 2

Establishes: The identifier and description.

  1. Record
  2. Record

Other links · 5

  1. Patch
  2. Patch
  3. Repository
  4. Repository
  5. Link

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-131852

Is CVE-2026-131852 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

What does this mean?

A format string flaw in OwnTracks Recorder lets a stored tid value containing printf specifiers be processed as format commands when it is read back. The advisory says this allows unauthenticated attackers to execute code by storing a malicious tid value, and it also mentions leaking addresses and writing memory.Source: vulncheck.com

Which versions are affected by CVE-2026-131852?

Recorder: before 1.0.5.Source: cve.now feed data

Am I affected, and how do I check?

Recorder versions before 1.0.5 are affected. The setup involves publishing locations with printf specifiers in tid via POST /pub or MQTT and later reading them back through GET /api/0/last. To check a installation, look at the Recorder version and whether these publish paths are in use.Source: vulncheck.com

How do I fix CVE-2026-131852?

Upgrade OwnTracks Recorder to 1.0.5, which is the listed fixed version.Source: vulncheck.com

More CVEs