External risk intelligence

OwnTracks Recorder Format String Vulnerability Allows Code Execution

CVE advisorySeverity: CRITICAL (CVSS 9.3)

CVE-2026-131852

OwnTracks Recorder is designed to receive location data via HTTP POST and MQTT endpoints. Because it functions as a data collection service that is frequently exposed to receive updates from remote mobile clients, it is commonly deployed as an internet-facing service or reachable via public-facing APIs.

Halo Surface Signal: 4 out of 5 — likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

A vulnerability has been identified in OwnTracks Recorder that could allow attackers to execute code by sending specially crafted location data. This could potentially lead to unauthorized access and manipulation of location information if the affected technology is in use. The main concern is confirming relevance and exposure.

  • Flaw allows code execution via location data.
  • Unauthenticated remote code execution risk.
  • Confirm if this technology is used.

Attack Path

How an attacker could exploit the issue

An attacker can initiate an attack by publishing location data containing malicious format string specifiers in the `tid` field to the OwnTracks Recorder. This data is stored and can then be retrieved through an API endpoint. By observing the output of these functions, an attacker may be able to infer memory addresses and potentially overwrite arbitrary memory locations, leading to code execution.

  • No authentication or user interaction needed.
  • Store malicious `tid` value for retrieval.
  • Unauthenticated code execution.

Live Threat

Current exploitation, exposure, and threat context

This vulnerability could allow an unauthenticated attacker to execute code by sending specially crafted location data. This could lead to the disclosure of memory contents or the modification of arbitrary memory addresses, potentially impacting the integrity and confidentiality of the system.

  • System memory and addresses at risk.
  • Malicious data via POST or MQTT.
  • Unauthenticated code execution and data leaks.

Operational Fix

Recommended remediation, mitigation, and detection steps

The OwnTracks Recorder's format string vulnerability requires immediate attention from teams managing the application and its underlying infrastructure. Given its function as a data collection service, the first practical step is to identify all instances of the affected technology, confirm their reachability and criticality, and then assign an owner for remediation planning.

  • Application owners are responsible for the issue.
  • Verify network exposure and critical assets first.
  • Plan remediation based on identified risks.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is OwnTracks Recorder?

OwnTracks Recorder is a server-side software component used to store and manage location data sent from mobile devices. It acts as a backend service that collects and logs location updates, which users can then retrieve and visualize. The application processes incoming data streams from mobile clients through web-based APIs or MQTT messaging protocols to keep a history of geographic positions.

What is the format string vulnerability in CVE-2026-131852?

This vulnerability, classified as CWE-134, occurs when software takes user-provided input and passes it as a formatting argument to functions like printf. In CVE-2026-131852, attackers can insert specific formatting characters into a location identifier field. When the recorder processes this data, the application mistakenly interprets these characters as programming instructions rather than plain text, allowing for unauthorized memory access or code execution.

How can an attacker trigger this vulnerability?

An attacker can trigger this by submitting a specially crafted location update containing malicious formatting codes to the recorder's POST or MQTT endpoints. The vulnerability is activated when the recorder later outputs this stored data through its API. It is important to note that simply sending the data does not immediately execute code; the system must process and then return that stored, malicious identifier to a user for the memory manipulation to occur.

Is my OwnTracks Recorder deployment at risk?

According to Halo Surface Signal, this software is frequently deployed as an internet-facing service or is reachable via public-facing APIs to receive updates from remote mobile clients. If your instance is accessible from the internet to facilitate data collection, it faces a higher level of risk. Internal-only deployments that do not accept traffic from untrusted networks are less likely to be directly reachable by external attackers.

What should I do to address CVE-2026-131852?

Start by identifying all instances of OwnTracks Recorder running in your environment. Once you have a complete inventory, verify the network reachability of these systems to understand which are exposed. Assign ownership to the relevant technical teams and plan to update the software to version 1.0.5 or later, which contains the necessary code changes to sanitize input and prevent this class of vulnerability.

References