/

CVE-2026-72577

Severity:

CRITICAL RISK

(9.8)

Missing Authentication (CWE-306) in NASA fprime-gds

CVE-2026-72577

Deferred

Vulnerability type

Category:

Missing Authentication

CWE:

CWE-306

Impact:

Remote Code Execution and Unauthorized Spacecraft Command Injection

Severity:

CRITICAL RISK

(9.8)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

NASA fprime-gds through version 3.4.3 exposes Flask application endpoints without authentication. An unauthenticated remote attacker may execute arbitrary code on the ground station host and inject commands into connected spacecraft.

Affected context

The vulnerability occurs in deployments of the fprime-gds Flask application where endpoints are reachable without an authentication layer. Risk is increased when the ground station host or its network interfaces are accessible to untrusted remote users and the application can communicate with connected spacecraft.

Exploit preconditions

  • Attack surface: Network-accessible Flask application endpoints
  • Required access: No authentication or prior authorization
  • Trigger point: Requests sent to exposed application endpoints
  • Why exploitation is possible: The application does not require identity verification before processing endpoint requests, allowing unauthenticated users to reach sensitive functionality

Why this happens

The underlying issue is missing authentication on application endpoints, mapping to CWE-306: Missing Authentication for Critical Function. The Flask application permits requests to reach sensitive operations without first establishing and enforcing the caller's identity, authorization, and permitted scope.

Potential impact

  • An attacker may execute arbitrary code on the ground station host
  • An attacker could compromise ground station processes and data
  • Unauthorized commands may be injected into connected spacecraft
  • Spacecraft operations or mission data could be disrupted
  • The compromise may enable further lateral movement within connected mission networks

General mitigation guidance

Mitigation generally focuses on enforcing authentication and authorization consistently across every endpoint that handles sensitive operations.

Common defensive patterns include:

  • Requiring strong authentication before exposing administrative or command-related functions
  • Applying endpoint-level authorization and least-privilege scopes
  • Placing the Flask service behind a controlled access gateway or private network boundary
  • Separating read-only telemetry functions from spacecraft command capabilities
  • Using secure-by-default deployment configurations that do not expose unauthenticated endpoints
  • Restricting ground station service privileges and outbound command permissions
  • Requiring explicit approval or policy checks for sensitive spacecraft commands

How teams detect issues like this

Organizations can identify missing authentication through:

  • Static analysis checks for Flask routes that lack authentication or authorization decorators
  • Code review of every route handling commands, administrative actions, or host-level operations
  • Dynamic endpoint inventories that flag sensitive routes accessible without credentials
  • Integration tests verifying unauthenticated requests are denied by default
  • Network policy checks for unintended exposure of ground station services
  • Automated security review tools that detect publicly reachable functions without access-control enforcement

Sources

SourceLink
github.comgithub.com/nasa/fprime-gds
github.comgithub.com/nasa/fprime-gds/blob/main/src/fprime_gds/flask/commands.py
github.comgithub.com/nasa/fprime-gds/blob/main/src/fprime_gds/flask/updown.py
pypi.orgpypi.org/project/fprime-gds/

Frequently asked

questions

Yes. The described attack surface is a network-accessible Flask application, and exploitation may be possible remotely when its endpoints are reachable by an attacker.

No. The issue is that the application applies no authentication to its endpoints, so an attacker may not need valid credentials to reach affected functionality.

Require authentication and endpoint-specific authorization before processing sensitive requests, while limiting each identity to the minimum required privileges.

Use deny-by-default access control, test every route for authentication coverage, isolate command-capable services, and enforce network and privilege policies around ground station systems.

Find out what's already
exploitable in your codebase.