External risk intelligence

AMMOS Instrument Toolkit BSC Path Traversal Leading to File Append

CVE advisorySeverity: CRITICAL (CVSS 9.1)

CVE-2026-47731

The software is designed for specialized mission control, satellite telemetry, and ground support equipment. These systems are inherently intended for isolated, highly secured, and restricted internal networks rather than public internet exposure. Although the API may be reachable locally, it is not a service typically exposed to the public internet in common, secure operational deployments.

Path Traversal

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

The AMMOS Instrument Toolkit, used for mission control and satellite data handling, has a vulnerability in its Binary Stream Capture component. This allows an unauthenticated attacker to potentially write to arbitrary files on the system by exploiting a path traversal weakness in an HTTP API. The main concern is confirming if this specialized software is in use and exposed to such risks within the organization.

  • Software can be tricked into writing to wrong files.
  • Confirms relevance and exposure of specialized systems.
  • Assess if this specific tool is deployed.

Attack Path

How an attacker could exploit the issue

An attacker could exploit this vulnerability by sending specially crafted requests to the Binary Stream Capture (BSC) component of the AMMOS Instrument Toolkit. This could be done directly over the network if the BSC service is exposed, or indirectly if the attacker can lure a user on the same network into visiting a malicious website. The vulnerability allows an attacker to write arbitrary data to any file on the system that the `ait-bsc` process has permission to access.

  • Network access or local network compromise required.
  • Unauthenticated HTTP API for packet capture.
  • Arbitrary file write and potential denial of service.

Live Threat

Current exploitation, exposure, and threat context

The Binary Stream Capture component of the AMMOS Instrument Toolkit, when deployed with a publicly accessible network port or exploited through a compromised local website, could allow a remote attacker to append arbitrary data to any file on the system, using the privileges of the `ait-bsc` process. This could impact system integrity and potentially sensitive log files.

  • Arbitrary file append on server.
  • Path traversal via HTTP API.
  • System integrity and log file compromise.

Operational Fix

Recommended remediation, mitigation, and detection steps

The AMMOS Instrument Toolkit's Binary Stream Capture component is susceptible to path traversal and arbitrary file append vulnerabilities. This impacts operations that utilize this component, potentially allowing remote attackers to compromise system integrity and availability. Ownership likely falls to the teams managing the specific instrument missions or ground data systems leveraging this toolkit, requiring an immediate inventory of affected systems, confirmation of network exposure and business criticality, and engagement with the accountable application or platform owners to plan remediation.

  • Identify and own affected systems.
  • Verify BSC accessibility and criticality.
  • Plan and coordinate remediation actions.

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 the AMMOS Instrument Toolkit used for?

The AMMOS Instrument Toolkit, formerly known as BLISS, is a Python-based software suite used in space missions. It manages ground data systems, electronic ground support equipment, and critical telemetry functions, including commanding, uplink, and downlink for instruments and CubeSat missions.

What does CWE-22 mean for CVE-2026-47731?

CWE-22 refers to Improper Limitation of a Pathname to a Restricted Directory, commonly known as path traversal. In this CVE, the Binary Stream Capture component fails to properly validate path-related form fields. This allows an attacker to escape the intended log directory and write or append data to arbitrary files on the underlying filesystem.

How can an attacker trigger this vulnerability?

An attacker can trigger this by sending specially crafted HTTP requests to the Binary Stream Capture API. This can happen directly if the service is network-accessible. Alternatively, it can occur indirectly if a user on the same network visits a malicious website, which uses browser-based scripts to send unauthorized requests to the local server, even if the service is restricted to localhost.

Is my system at risk according to Halo Surface Signal?

Halo Surface Signal indicates that while the API is reachable locally, the risk is rated as 'Very unlikely' for public internet exposure. Because this software is designed for specialized satellite mission control and ground support equipment, these systems are typically deployed within isolated, highly secured, and restricted internal networks rather than being exposed to the public internet.

What steps should I take if I use AIT-Core?

You should verify if your infrastructure utilizes the affected versions of AIT-Core and identify where the Binary Stream Capture component is running. The primary response is to update your software to version 3.1.1 or 2.6.1, which addresses the path traversal flaw. Coordinate with your mission control or system administration teams to inventory deployments and prioritize these updates.

References