External risk intelligence

OpenTracks Tracking Data Injection Vulnerability

CVE advisorySeverity: CRITICAL (CVSS 9.1)

CVE-2026-107056

This vulnerability exists within a specific mobile application component (ImportActivity) that processes local file imports or inter-app messages. It is not an internet-facing service, edge gateway, or network-reachable API. The attack surface is limited to the local environment of the device, typically requiring user interaction or specific local conditions to trigger.

Halo Surface Signal: 1 out of 5 — much less likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

This advisory concerns a critical vulnerability within the OpenTracks application. An issue with how permissions are handled allows an attacker to insert malicious location data into the app's database. While the application itself is not typically internet-facing, the ability to manipulate location data could have implications if the app's data is used in downstream systems or processes.

  • Insecure permissions allow data injection.
  • Location data integrity is compromised.
  • Confirm relevance and assess potential data manipulation.

Attack Path

How an attacker could exploit the issue

An attacker could exploit this vulnerability by sending a specially crafted message to the OpenTracks application on a victim's device. This message, when processed by the `io.file.importer.ImportActivity` component, could allow the attacker to insert malicious data into the user's location database.

  • Entry condition: No special access required.
  • Trigger point: Sending a crafted SEND message.
  • Resulting risk: Unauthorized modification of location data.

Live Threat

Current exploitation, exposure, and threat context

When supported by the advisory, an attacker could inject crafted tracking data into a user's location database by sending a specially made message to the io.file.importer.ImportActivity component.

  • Location data could be affected.
  • Via a crafted SEND message.
  • Data integrity may be compromised.

Operational Fix

Recommended remediation, mitigation, and detection steps

This vulnerability resides within a mobile application component and requires local interaction or specific message passing on the device, limiting its internet-facing exposure. The primary action is to identify affected devices, assess the criticality of the data stored within the application, and confirm the accountable application owner or responsible team for the device. Once identified, a remediation plan can be developed based on the assessed risk.

  • Confirm application owner and device exposure.
  • Verify app reachability and data criticality.
  • Plan remediation based on risk assessment.

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 OpenTracks?

OpenTracks is an open-source Android application used for recording GPS tracks and physical activities. It allows users to log their movements, such as running, cycling, or hiking, storing this data locally on their mobile device for later review or export.

What does CWE-732 mean for CVE-2026-107056?

CWE-732 refers to incorrect permission assignment for a critical resource. In this case, the OpenTracks component responsible for importing files does not properly restrict who can interact with it, allowing unauthorized processes to influence its internal functions.

How can an attacker trigger this vulnerability?

An attacker can trigger this by sending a specially crafted SEND message to the app's ImportActivity component. It is important to note that simply browsing the app or viewing existing tracks does not trigger this issue; it requires a specific, intentionally malformed message to be processed by the component.

Is my device at risk if OpenTracks is not internet-facing?

According to Halo Surface Signal, this vulnerability is very unlikely to be exploited remotely because it is not an internet-facing service. The risk is limited to the local device environment, meaning an attacker generally needs the ability to send messages directly to the application on your phone.

How should I respond to this vulnerability?

Start by identifying if you have the affected version of OpenTracks installed. Since this is a local mobile application issue, review the importance of the location data you store in the app. Coordinate with your device management team to monitor for updates or official guidance on securing the application's data imports.

References