External risk intelligence

AMMOS AIT DSN Missing Authentication in SLE API Routes

CVE advisorySeverity: CRITICAL (CVSS 9.3)

CVE-2026-60113

The affected component is the Deep Space Network Interface within the AMMOS Instrument Toolkit, a specialized system for spacecraft communication. Such software is inherently restricted to dedicated, mission-critical infrastructure and is not designed for public internet deployment or general-purpose network exposure.

Missing Authentication

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

A vulnerability has been identified in a specialized interface used for managing Deep Space Network communications. This issue could allow unauthorized parties to control communication sessions, access critical data, or inject false information into active spacecraft links. The primary concern is to confirm if this specific, highly specialized technology is present within our environment.

Unauthenticated access to critical spacecraft communication controls.
Critical for specialized space communication systems.
Verify relevance and exposure within our environment.

Attack Path

How an attacker could exploit the issue

An unauthenticated attacker on the network can access unprotected API routes within the AMMOS Instrument Toolkit's Deep Space Network Interface. By sending direct HTTP requests without credentials, attackers can manipulate Deep Space Network communication sessions, retrieve telemetry data, and inject frames into active spacecraft links.

No authentication required.
Direct HTTP requests to API routes.
Unauthorized control of network sessions.

Live Threat

Current exploitation, exposure, and threat context

The AMMOS Instrument Toolkit's Deep Space Network interface could allow unauthenticated attackers to interfere with spacecraft communication. When supported by the advisory, attackers could directly access unprotected API routes to control communication sessions, access telemetry data, or inject malicious frames into active links.

Deep Space Network communication sessions at risk.
Direct HTTP requests to unprotected API routes.
Disruption of critical spacecraft communications.

Operational Fix

Recommended remediation, mitigation, and detection steps

The AMMOS Instrument Toolkit's Deep Space Network Interface is likely managed by specialized infrastructure or platform teams responsible for space communication systems. The first practical step is to confirm the deployment location of this toolkit, assess its connectivity, and determine its criticality to ongoing or planned missions to identify the accountable owner and prioritize remediation efforts.

Infrastructure or platform teams own the issue.
Verify network reachability and criticality.
Plan vendor coordination and remediation.

Supplementary metadata

CVSS vector

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.

Free EASM Trial See How Signal Works

Frequently asked questions

What is the AMMOS Instrument Toolkit (AIT) DSN Interface?

The AMMOS Instrument Toolkit (AIT) is a specialized software framework developed by NASA for spacecraft instrument testing and operations. The Deep Space Network (DSN) Interface component acts as a bridge for managing communications between ground systems and space-based assets. It is primarily used by engineers and mission teams to handle telemetry data, manage communication sessions, and ensure reliable data exchange with spacecraft operating in deep space environments.

What does CVE-2026-60113 mean?

This vulnerability is classified as a 'Missing Authentication for Critical Function' (CWE-306). In plain English, the software fails to verify the identity of anyone trying to access specific administrative API routes. Because these routes are left unprotected, the system treats unauthorized requests as legitimate commands, effectively bypassing security barriers that should be protecting sensitive spacecraft communication controls.

How can an attacker trigger this vulnerability?

An attacker can exploit this by sending specially crafted, unauthenticated HTTP requests directly to the affected API endpoints. No special interaction or existing credentials are required to initiate these commands. It is important to note that this bug specifically resides within the Space Link Extension (SLE) interface manager; it does not impact other, properly secured parts of the broader AMMOS toolkit.

Is my system at risk according to Halo Surface Signal?

Halo Surface Signal indicates that this risk is very unlikely for most environments. The AIT-DSN Interface is designed for highly specialized, mission-critical infrastructure rather than general-purpose use. Because this software is typically kept within isolated or dedicated space communication networks, it is generally not exposed to the public internet, which significantly limits the reach of potential attackers.

What should I do if I run AIT-DSN?

Your first step is to locate all instances of the toolkit within your infrastructure and confirm their network connectivity. Since this is mission-critical software, verify who is responsible for these systems and coordinate with them to assess the exposure. Prioritize identifying if these interfaces are reachable from untrusted networks and prepare to apply the update to version 2.2.2 or later, which addresses the authentication deficiency.

References

Written by Nicholas Merritt

Nicholas Merritt is VP of Security Solutions at Halo Security. With more than 25 years across application security, vulnerability prioritization, and offensive security, he helps teams translate threat data into practical exposure validation and remediation focus. He authors Halo Threat Intelligence CVE advisories using Halo Surface Signal and H/A/L/O context to prioritize internet-facing risk.