Skip to main content

NASA AIT-Core EUVDEUVD-2026-92014

| CVE-2026-105105 CRITICAL
Missing Authentication for Critical Function (CWE-306)
2026-10-03 TuranSec GHSA-9xfm-37f4-2h8g
9.8
CVSS 3.1 · Vendor: TuranSec
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Reach ground network ZeroMQ bus
  2. Delivery
    Connect to broker TCP 5559
  3. Exploit
    Publish to __commands__ topic
  4. Execution
    Commands forwarded via command_stream
  5. Impact
    Forged commands uplinked to spacecraft

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A07:2025 - Authentication Failures
ASVS 5.0
V6 - Authentication Authentication required for critical functions
MITRE ATT&CK

1 technique across 1 tactic: Initial Access

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Requires network-level reachability to the ait-server ZeroMQ message bus - specifically TCP port 5559 (XSUB) to publish spacecraft command data onto internal topics including __commands__, and/or TCP port 5560 (XPUB) to subscribe to command and telemetry traffic. The vulnerable state is the DEFAULT configuration in AIT-Core through 3.1.1, where the broker binds XSUB/XPUB to all network interfaces with no authentication or transport security; command forwarding to the uplink UDP path specifically relies on the shipped default command_stream configuration. Limiting factors: the attacker must have a network path to the ground bus (typically an isolated/segmented mission network rather than the internet), and upgrading to 3.1.2 - which binds these sockets to loopback by default - removes remote reachability entirely.

Impact

All available signals point to a genuine high-priority issue rather than a CVSS-inflated one. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N, C:H/I:H/A:H = 9.8) is consistent with the description: the ait-server ZeroMQ broker binds its XSUB/XPUB sockets to all interfaces by default with no authentication or transport security, so any attacker reaching TCP 5559/5560 can publish or subscribe. This is unauthenticated (PR:N confirmed by vector) and requires no user interaction, matching the kill-chain impact of command injection and telemetry exfiltration. No EPSS score, CISA KEV listing, or public POC was provided in the input, so there is no public exploit identified at time of analysis and exploitation probability cannot be quantified. The key mitigating reality not captured in the raw 9.8 is deployment topology: ait-server is spacecraft ground-system software normally run on segmented mission networks, so 'network access to the ZeroMQ bus' in practice means an attacker already positioned on or adjacent to the ground network, not the open internet. Note a cross-reference caveat: one linked advisory (GHSA-3j6g-pxmx-58qg) concerns a DIFFERENT product, AIT-GUI before 2.5.1 (unauthenticated Sessions.create/handle_cmd), not AIT-Core - related missing-auth theme but should not be conflated with this CVE when assessing affected versions.

Exploit ScenarioDerived

An attacker with reachability to the mission ground network connects to the ait-server ZeroMQ broker on TCP 5559 and publishes crafted messages onto the __commands__ topic; with the shipped default configuration these are forwarded through command_stream and emitted on the command-uplink UDP path as spacecraft commands. The same attacker can subscribe on TCP 5560 to passively exfiltrate live command and telemetry traffic or inject forged telemetry to mislead operators. No public exploit code was identified in the provided data, but exploitation requires no authentication or special tooling beyond a standard ZeroMQ client.

Act Now Prioritize within 24-48h. Why: CRITICAL severity.
No patch listed yet 0.8% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 03, 2026

Unauthenticated spacecraft command injection and telemetry exfiltration in NASA-AMMOS AIT-Core through 3.1.1: the ait-server ZeroMQ telemetry and command broker binds its XSUB (TCP 5559) and XPUB (TCP 5560) sockets to all network interfaces by default with no authentication or transport security, so any unauthenticated remote attacker with a network path to the ground bus can publish onto internal topics including __commands__, push forged commands through command_stream onto the command-uplink UDP path, subscribe to live command and telemetry traffic, or disrupt the bus outright. The assessed CVSS 3.1 base score is 9.8 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H), reflecting unauthenticated, low-complexity remote exploitation that fully compromises confidentiality, integrity, and availability of the command and telemetry path; no public exploit code has been identified at time of analysis, and this CVE is not in CISA KEV. The exposure is conditional on the shipped default configuration - exploitation requires network reachability to ports 5559 and/or 5560, which is typically an isolated or segmented mission network rather than the public internet - and the fix is AIT-Core 3.1.2, which rebinds these ZeroMQ sockets to loopback by default.

RemediationAI

Vendor-released patch: AIT-Core 3.1.2, which changes the default ZeroMQ bind addresses to loopback and therefore removes remote reachability to the broker sockets - upgrade all ait-server instances to 3.1.2 or later. If an immediate upgrade is not possible, explicitly rebind the XSUB and XPUB sockets to 127.0.0.1 (or a single designated internal interface) in the ait-server configuration, for example replacing a wildcard bind on TCP 5559 and TCP 5560 with a loopback bind; the trade-off is that legitimate remote subscribers and publishers (telemetry displays, remote command clients) will lose connectivity and must instead be reached through an authenticated tunnel or a local forwarder. Complement this by enforcing host-firewall rules and network segmentation so only authorised ground-segment hosts can reach TCP 5559 and TCP 5560 - note this reduces reachability but does not add authentication, so anything on the permitted segment remains trusted. Where the broker must remain multi-host, enable ZeroMQ CURVE authentication with a ZAP handler (and encryption) so peers must present keys before publishing or subscribing; the trade-off is key distribution and client-side configuration changes across the ground system. Also restrict the downstream command-uplink UDP path so that injected __commands__ messages cannot be re-forwarded to the spacecraft, and audit the command_stream configuration for the default forwarding behaviour described in the advisory. Consult https://github.com/NASA-AMMOS/AIT-Core/security/advisories/GHSA-ccw5-g774-3683 for vendor guidance, and separately apply the AIT-GUI fix (advisory https://github.com/advisories/GHSA-3j6g-pxmx-58qg, commit beb8fc0813eded89f985d3eb9a73535dd327726d) if the GUI component is in use.

Affected VersionsENISA

AIT-Core 0 ≤3.1.1

Affected Packages

euvd ait_core no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

NASA-AMMOS AIT-Core is the Python 'AMMOS Instrument Toolkit' ground data system framework used to build spacecraft telemetry and command pipelines; ait-server acts as the central ZeroMQ broker that relays traffic between producers and consumers of the ground bus. ZeroMQ's XSUB/XPUB pattern is a message-forwarding proxy: publishers connect to XSUB (TCP 5559) and their messages are relayed to all subscribers attached to XPUB (TCP 5560), with topic-prefix filtering. The root cause is CWE-306 (Missing Authentication for Critical Function): the broker exposes the critical publish/subscribe operation on every interface with no credential check and no transport security - no ZeroMQ CURVE/ZAP, no TLS - so message origin is unverifiable and payloads are in cleartext. In the vulnerable default configuration through 3.1.1 the bind address is permissive (all interfaces); once an attacker reaches TCP 5559 they can inject messages onto any topic, including the reserved __commands__ topic, and the shipped default command_stream configuration forwards those messages onto the command-uplink UDP path. Reaching TCP 5560 is enough to passively collect command and telemetry traffic. The CPE cpe:2.3:a:nasa-ammos:ait-core:*:*:*:*:*:*:*:* captures the wildcard version range, i.e. all releases up to and including 3.1.1. AIT-Core 3.1.2 mitigates by changing the default ZeroMQ bind addresses to loopback, which removes remote reachability without altering the underlying protocol. A closely related but distinct missing-authentication issue affects AIT-GUI before 2.5.1 (GHSA-3j6g-pxmx-58qg), where Sessions.create() issues a valid session with no credential check and handle_cmd() then dispatches arbitrary commands to the bus; that defect is fixed in commit beb8fc0813eded89f985d3eb9a73535dd327726d and shares the same trust-boundary failure.

Know when Ait Core gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (TuranSec) PRIMARY 9.8 CRITICAL
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
vuln.today AI 9.8 CRITICAL

Default all-interface bind with no auth gives AV:N/AC:L/PR:N/UI:N; attacker can read traffic (C:H), inject commands/forge telemetry (I:H), and disrupt the bus (A:H).

3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
4.0 AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (TuranSec).

CVSS VectorVendor: TuranSec

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

DescriptionCVE.org

CWE-306: Missing Authentication for Critical Function in the ait.core.server telemetry and command broker (ait-server) in NASA-AMMOS AIT-Core through 3.1.1 allows an unauthenticated remote attacker with network access to the ZeroMQ message bus to inject spacecraft command data, exfiltrate command and telemetry traffic, inject forged telemetry, or disrupt the command and telemetry bus. The ait-server ZeroMQ broker binds its XSUB and XPUB sockets to all network interfaces by default without authentication or transport security. An attacker able to reach TCP port 5559 can publish messages onto internal topics, including the __commands__ command topic. With the shipped default configuration, command messages are forwarded through command_stream and emitted on the command-uplink UDP path. An attacker able to reach TCP port 5560 can subscribe to command and telemetry traffic on the ground bus. AIT-Core 3.1.2 changes the default ZeroMQ bind addresses to loopback.

Technical POC Analysis

CWE-306: Missing Authentication for Critical Function in ait.core.server, specifically the ait-server ZeroMQ telemetry/command broker.

Full technical POC analysis - root cause, step-by-step exploitation and patch breakdown - is part of the Pro and Business plans.

Executive ViewAI

Why It Matters

NASA-AMMOS AIT-Core (through version 3.1.1), an open-source ground-segment framework that brokers spacecraft commands and telemetry, ships in a default configuration that exposes its command and telemetry sockets to any host with a network path to the ground bus and requires no authentication. Because those sockets carry the command uplink path, an unauthenticated attacker on that network could inject forged spacecraft commands, read live telemetry, or disrupt the bus entirely, turning a software misconfiguration into a potential safety-of-flight and mission-assurance event. No public exploit code has been identified at time of analysis, and exposure is conditional on the shipped default configuration and network reachability, so leadership should treat this as a ground-segment hardening priority rather than an active incident.

Business Impact: High
Compensating Controls

No vendor-released patch identified at time of analysis. Interim mitigations: bind ait-server XSUB/XPUB sockets to localhost or a single trusted interface instead of all interfaces; block TCP 5559 and 5560 with host and network firewalls so only authorized ground-segment hosts have a network path to the broker; segregate the command/telemetry bus onto an isolated, non-routable network segment; enable available broker authentication and transport encryption (e.g., ZeroMQ CURVE) and restrict publish authorization on the __commands__ topic; monitor and alert on anomalous publishers, unexpected command_stream activity, and inbound connections to the broker ports.

Threat Intelligence Overview

EPSS Score
0.8%
Top 46% exploitable
Prevalence
Low
niche NASA/AMMOS spacecraft ground-system software, aerospace-mission-specific footprint
Social Media
5
Sightings
Data Quality
7 sources
Confidence: High
EUVD NVD CVE.org EPSS Vulnrichment CIRCL GitHub VulDB

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity CRITICAL
CISA KEV No
Public POC No
EPSS 0.8%
Patch available No
Active threat No
Deciding rule
CRITICAL severity
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
Yes
Human Impact
High
Technical Impact
Total

Priority Score

50
Low Medium High Critical
KEV: 0
EPSS: +1
CVSS: +49
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy