On this page (7 sections)

A critical vulnerability, CVE-2026-131852, was published on 2026-11-18 for OwnTracks Recorder. According to the GitHub Advisory, versions before 1.0.5 contain a format string flaw in json_response() and related output functions that unauthenticated attackers can use to execute code by storing a malicious tid value.

If you self-host a Recorder instance, especially one reachable from the internet over HTTP or fed by an MQTT broker, check your version now and plan an upgrade to 1.0.5 or later. Sourcing is thin so far, so the details below are limited to what the advisory text states.

What happened

The flaw was published through the National Vulnerability Database and the GitHub Advisory Database on November 18, 2026. The description says an unauthenticated attacker can store a malicious value in the tid field and later read it back through an API endpoint, which leads to a format string problem in Recorder's output functions.

The advisory references a fix commit, a pull request, a 1.0.5 release tag and a VulnCheck advisory. We have only the advisory text for these, not their contents, so confirm the details there yourself.

Sourcing is thin. The NVD entry repeats the GitHub Advisory text and is not independent confirmation. The GitHub entry is marked unreviewed and lists affected and patched versions as unknown at the package level, so the 'before 1.0.5' range comes from the vulnerability description itself.

Technical details

As general background, a format string bug happens when a program passes data it did not control to a printf-style function as the format instead of as a plain value. Specifiers in that data are then interpreted as instructions, which can reveal memory contents or write to memory. That is why this weakness class (CWE-134) can lead to code execution.

What is notable here is that the dangerous input is stored first and used later. Per the advisory, an attacker publishes locations via POST /pub or MQTT with printf specifiers in tid, then reads them back through GET /api/0/last. The advisory says this leaks addresses and writes memory. It points to the http.c file in version 1.0.4 for the affected code.

The CVSS v4 metrics shown in the GitHub Advisory are network attack vector, low attack complexity, no attack requirements, no privileges and no user interaction, with high impact to confidentiality, integrity and availability of the vulnerable system. In plain terms, no login is needed if the endpoints are reachable.

Who is affected

Any deployment of OwnTracks Recorder older than 1.0.5 is in scope. Practical exposure depends on setup:

  • Instances whose HTTP interface is reachable from the internet, since the attack uses POST /pub and GET /api/0/last.
  • Setups where MQTT messages from untrusted clients can reach Recorder, since the advisory names MQTT as a publishing path.
  • Instances reachable only on a private network or VPN are less exposed, but anyone who can reach them or publish through the broker could still be a risk.

The research does not say which configurations require authentication by default, so do not assume your instance is protected. Verify it.

How to check your exposure

The research does not name any distribution package or version command for Recorder, so there is no single command we can give you. Work out the version from how you installed it:

  • If you built from source or downloaded a release, compare the release or tag you used with the 1.0.5 tag.
  • If you use a container image, look at the image tag you deploy.
  • If you installed through a package manager, use that manager's own query for the package you installed. The research lists no package, so do not assume a standard package name exists.

Then review which hosts and networks can reach the HTTP interface and the MQTT broker. If either is open to the internet or to untrusted clients and you run a version before 1.0.5, treat the instance as exposed.

What to do now

  1. Identify every Recorder instance you run, including test and personal ones, and note the version.
  2. Upgrade to 1.0.5 or later using the method you installed with, and review the 1.0.5 release page and the project's own notes to confirm the fix.
  3. Until you can upgrade, restrict access: put the HTTP interface behind a VPN or authenticated reverse proxy and limit who can publish to your MQTT broker.
  4. Review stored location data and request logs for tid values containing printf-style specifiers such as percent signs, and for unexpected requests to /pub and /api/0/last.
  5. If you find signs of tampering or unexpected activity on the host, treat it as possibly compromised and follow your incident response process, for example rebuilding from a known-good state and rotating credentials stored on it.
  6. After upgrading, confirm the running version is 1.0.5 or later and that the service works normally.
Caution. Upgrading will likely restart the Recorder service and briefly interrupt location publishing and reads. Back up your data and configuration before you start.

Detection and monitoring

Because the attack stores a value and reads it back, traces would most likely appear in request logs from your reverse proxy or broker: POST requests to /pub or MQTT publishes from unfamiliar clients, followed by reads of /api/0/last. Whether Recorder's own logs record tid values depends on your configuration, so any search for percent-sign sequences is only a heuristic and a miss does not prove you are clean.

Alert on tracker IDs that do not match your known devices, and watch the host for unexpected processes, outbound connections or service crashes. If your Recorder sits behind a public domain, certificate and DNS monitoring can flag unexpected changes, and a web application firewall in front of the HTTP interface can add filtering, though it is no substitute for patching.

What we do not know yet

  • No source in the research reports active exploitation, and the CVE has no CISA KEV entry in the data provided.
  • No public proof-of-concept or attacker activity is described in the sources, and this article does not provide any.
  • The GitHub entry lists patched versions as unknown, so confirm the fix version with the project.
  • Only one underlying advisory text exists so far. Details may change as the project or other researchers publish more.

For broader habits that reduce risk on internet-facing services, see our small business website security guide.

Sources

This article is based on the public sources below. Details can change as vendors and researchers publish more; check the original advisories before acting on version numbers.

  1. CVE-2026-131852 - GitHub Advisory Databasegithub.com
  2. CVE-2026-131852: OwnTracks Recorder before 1.0.5 contains a format string vulnerability in json_response() and related output functions that allows unauthenticated attackers…nvd.nist.gov ·
  • OwnTracks
  • CVE-2026-131852
  • format string
  • CWE-134
  • self-hosted
  • critical