NASA's flight software treats onboard modules as trusted peers

A malicious component compromised NASA's flight software without breaking a single access rule, per a new architectural analysis (arXiv 2608.14532). Five experiments on NASA's flight-representative NOS3 simulator confirmed the attack works using only legitimate architectural privileges. The same trust assumptions turn up in other modular flight software frameworks too, per the analysis, so the flaw isn't limited to NASA's code.

Core Flight Software gives every onboard component broad, shared authority over identity, communication, observability and persistence, per the analysis. A single compromised component can abuse that authority in ways the analysis found difficult to separate from legitimate behavior.

That architecture looks familiar outside aerospace. MCP, the protocol AI agents use to connect tools, hands every connected component the same broad permissions as the host process. A calendar plugin and a file-deletion plugin get treated the same way. Nobody has to write a bug to abuse that. They just have to be a plugin.