CVE-2026-72577 in Fprime-gds
Summary
by MITRE • 08/10/2026
Multiple vulnerabilities in NASA fprime-gds through 3.4.3 allow an unauthenticated remote attacker to achieve arbitrary code execution on the ground station host and inject arbitrary commands to connected spacecraft. The Flask application in src/fprime_gds/flask/app.py applies no authentication to any endpoint. A path traversal in src/fprime_gds/flask/updown.py allows reading and writing arbitrary files outside the upload directory. A hardcoded secret key (CWE-321) in the application enables session forgery. Chained together, these vulnerabilities allow complete compromise of the ground data system and any spacecraft under its control.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Analysis
by VulDB Data Team • 08/10/2026
The NASA fprime-gds software presents a critical security vulnerability landscape that fundamentally compromises the integrity and confidentiality of space mission ground systems. This ground data system serves as the primary interface for commanding and controlling spacecraft, making it a prime target for adversaries seeking to undermine mission operations. The vulnerabilities exist within the Flask-based web application framework that governs user interactions with the ground station, creating an attack surface that lacks fundamental authentication mechanisms across all endpoints. The absence of any form of access control creates an environment where unauthorized parties can immediately gain administrative privileges without requiring any credentials or authorization tokens.
The technical implementation flaw in the upload functionality within src/fprime_gds/flask/updown.py exposes a classic path traversal vulnerability that allows attackers to manipulate file system paths beyond the intended upload directory boundaries. This weakness enables arbitrary file reading and writing operations outside of designated safe zones, potentially allowing attackers to access sensitive configuration files, modify critical application components, or inject malicious code into the system. The vulnerability stems from insufficient input validation and sanitization of user-provided file paths, creating a direct pathway for file system manipulation that bypasses normal security boundaries.
A fundamental cryptographic weakness exists through the use of a hardcoded secret key within the application's configuration, representing a CWE-321 vulnerability that directly enables session forgery attacks. This hardcoded credential allows attackers to generate valid session tokens without legitimate authentication, effectively granting them persistent access to the system. The secret key serves as the foundation for cryptographic operations including session management and data integrity verification, making its exposure particularly dangerous for maintaining system security. Attackers can leverage this weakness to impersonate authorized users and maintain long-term access to the ground station infrastructure.
The chained nature of these vulnerabilities creates a complete compromise scenario where attackers can progress from initial unauthorized access through to full system control. The lack of authentication combined with path traversal capabilities and session forgery creates a multi-layered attack vector that allows adversaries to not only execute arbitrary code on the ground station host but also inject malicious commands directly into connected spacecraft systems. This represents a severe escalation from simple unauthorized access to complete mission control compromise, potentially enabling data exfiltration, system manipulation, or even deliberate spacecraft malfunction.
The operational impact of these vulnerabilities extends beyond traditional cybersecurity concerns to encompass critical mission safety and operational integrity. Spacecraft missions rely heavily on ground station communications for command execution, telemetry monitoring, and operational control, making any compromise of the ground data system a potential threat to mission success. The ability to inject arbitrary commands into spacecraft creates risks of orbital debris generation, mission failure, or even potential threats to other space assets in orbit. This vulnerability fundamentally undermines the trust model that governs space operations and could enable adversaries to disrupt critical infrastructure.
Mitigation strategies should include immediate implementation of robust authentication mechanisms across all application endpoints, comprehensive input validation for file path operations, and dynamic secret key generation rather than hardcoded values. The Flask application framework requires proper session management with secure token generation and storage practices that align with industry standards such as those defined in the OWASP Top Ten. Network segmentation and access controls should be implemented to limit exposure of the ground data system to authorized personnel only. Regular security assessments should include penetration testing of critical infrastructure components, particularly those handling spacecraft communications. The implementation of principle of least privilege access controls and monitoring solutions for detecting unauthorized access attempts would significantly reduce the risk profile of these systems. Organizations should also consider implementing multi-factor authentication mechanisms and regular credential rotation policies to maintain system security posture against evolving threats.