ELINT · Electronic Intelligence

SatBleed: the smallsat radio’s weakest key is held on the ground

A new analysis of commodity CubeSat transceivers finds 14 flaws, including a ground-station bug that leaks satellite command keys. Open telemetry suggests at least 28 satellites in orbit are exposed.

The radio is the root of trust

On a small satellite, the communication module is the one subsystem that must listen to the outside world all the time. It receives every telecommand, and the rest of the spacecraft trusts what it passes on. A paper posted to arXiv on 5 October 2026 shows that in commodity modules this trust is often misplaced [1]. Researchers from CISPA, the armasuisse Cyber-Defence Campus and the University of Hamburg examined three off-the-shelf UHF/VHF transceivers. They report vulnerabilities in firmware, protocols and architecture that affect dozens of missions [1]. The work was accepted at IEEE S&P 2026 [2][3]. The arXiv release puts the full text in front of a much wider audience.

The headline finding is not on the satellite. It is on the ground. The flaw the authors named SatBleed is a logic error in how a vendor ground-station front end handles telemetry. In the researchers’ words, it “allows an unauthenticated attacker to extract cryptographic material from ground stations” [1]. The material in question is the satellite’s own telecommand signing key [1]. Whoever holds that key can issue commands the spacecraft will accept as genuine.

What the paper measured

The study covered the GomSpace NanoCom AX100, with its GS100 ground-station front end, the UHF section of Libre Space Foundation’s open-source SatNOGS-COMMS, and the EnduroSat UHF Transceiver II [1]. Table II of the paper lists 14 findings: ten against GomSpace, two against Libre Space and two against EnduroSat [1]. Twelve are marked realistically exploitable. Seven are vendor-confirmed or demonstrated with a proof of concept [1].

The flaws fall into familiar classes. The authors found no replay protection in the CubeSat Space Protocol services on the module [1]. Authentication tags are short: a 32-bit truncated HMAC on the GomSpace part and a 4-byte tag on SatNOGS-COMMS [1]. Under the paper’s stated throughput assumption, forging a tag online could take under ten hours [1]. Debug and internal commands can disable authentication. One service exposes a function-pointer address that enables arbitrary memory access [1]. The EnduroSat update protocol, as tested, had no integrity check, so any device on the bus could push firmware [1]. Only SatNOGS-COMMS enforced secure boot [1]. GomSpace did not confirm that one debug protocol was intentional and said it is “not supposed to be used” [1].

The vendors’ own documentation explains part of the exposure. GomSpace’s product page lists a GOSH interface for check-out, test and debugging alongside CSP networking over I2C, UART and CAN [4]. Its 2020 AX100 manual describes HMAC as a receive-side filter keyed by a configurable parameter whose default value is all zeros [5]. The manual does not mention replay protection [5].

The authors then estimated exposure in orbit. They used telemetry published through the SatNOGS network, an open, crowd-sourced database of satellites and their transmitters [6]. At least 64 active satellites use the AX100. The authors infer that 28 of them are plausibly vulnerable to SatBleed: 12 transmit beacons without HMAC that the ground station can enforce, and 16 toggle that setting [1]. They call 28 a lower bound, because the method is passive and assumes firmware versions and ground-station configurations [1]. They have not published the mission list [1].

Two figures do not reconcile. The paper puts EnduroSat modules in orbit at more than 3,000 [1]. EnduroSat’s product page states 5,000 modules in orbit, as a company-wide figure [7]. The vendor also now advertises AES-256 encrypted links and secured in-flight updates for its UHF transceiver [7]. The paper labels the unit it tested as deprecated [1]. Readers should treat the EnduroSat findings as applying to the generation tested, not automatically to current stock. The SatNOGS-COMMS project page describes an open hardware and software design but no link-security features [8].

What it means

Three points matter for operators. First, the ground segment holds the keys, so ground-segment software is now part of the spacecraft’s attack surface. SatBleed turns a telemetry-handling bug on Earth into command authority in orbit [1]. NIST IR 8401 already applies the Cybersecurity Framework to satellite command and control on the ground [12]. This paper gives that profile a concrete failure case.

Second, standards exist that the tested defaults do not meet. The CCSDS Space Data Link Security protocol baseline uses 128-bit keys and 128-bit MACs for telecommand authentication. It also carries a 32-bit anti-replay sequence number [9]. Its designers noted that most civilian missions had no standard link security and relied on ad hoc schemes [9]. A truncated 32-bit tag with no replay window is the ad hoc scheme in practice.

Third, this is a pattern, not a one-off. In 2023, Ruhr-Universität Bochum researchers found that three low-orbit satellites lacked basic protections. Their developer survey described an industry relying on security through obscurity [10]. In 2024, a team including one of the SatBleed authors gained a root shell on a VSAT modem by RF signal injection, using commodity software-defined radio equipment [11]. That vendor did not answer for over a year [11]. In SatBleed, by contrast, GomSpace and EnduroSat acknowledged the reports. Both plan fixes in the next generation, and GomSpace plans fixes for some current models [1]. Satellites already in orbit, however, cannot have their hardware recalled.

What to do

  • Inventory every COTS communication module and ground-station front end by vendor, model and firmware version. Assume the paper’s 28-satellite figure understates exposure across product lines; the vendors confirmed that other subsystems in their portfolios share some flaws [1].
  • Treat ground-station software that handles telemetry as key-bearing infrastructure. Isolate it, restrict who can reach it, and log parameter requests that touch key material [1][12].
  • Replace default or shared HMAC keys before integration, and never fly with a default key parameter [5]. Where the link supports it, move to full-length MACs with anti-replay, aligned with the CCSDS SDLS baseline [9].
  • Verify telecommand signatures on the subsystem that executes the command, not only on the module that forwards it, and authenticate internal bus commands [1].
  • Disable or lock debug interfaces and serial ports before flight, and require signed firmware with secure boot where the hardware allows it [1][4].
  • Ask vendors for written disclosure-handling commitments and fix plans for fielded units. Map residual risks to a space-specific framework such as SPARTA when reporting to mission owners [13].
  • Audit what your beacon reveals. If open receivers can tell whether your telemetry is authenticated, so can an adversary [1][6].

The ELINT read

The method is the lesson. The researchers did not touch an operational link [1]. They inferred security posture from emissions any amateur station can receive and that the SatNOGS network publishes openly [1][6]. That is signals intelligence against configuration, performed with public data. A capable collector can do the same thing with more patience and no ethics board. Commodity UHF modules are fitted to many university and commercial CubeSats [1]. For these missions, the beacon itself is an intelligence emission, and the uplink is an RF attack surface that needs no network access. Programmes building or buying smallsats should treat their telemetry design as a disclosure decision and their ground station as a cryptographic asset. The authors say they are in discussions with federal institutions and may contact critical missions directly [1]. Operators should not wait for that call.

Sources

Every R3KONX article cites its primary material. 13 sources, in order of first citation. Links open the original publication.

  1. SatBleed: Security of Commoditized Communication Modules in Satellites (arXiv:2610.06258v1) arXiv / CISPA Helmholtz Center for Information Security, armasuisse Cyber-Defence Campus, University of Hamburg · 2026-10-05
  2. SatBleed: Security of Commoditized Communication Modules in Satellites (publication record) CISPA Helmholtz Center for Information Security · 2026-05-18
  3. Paper on satellite security at S&P 2026 University of Hamburg, Department of Informatics · 2026-05-04
  4. NanoCom AX100: Flexible and Miniaturised Transceiver (product page) GomSpace · 2026-10-18
  5. NanoCom AX100 Manual, release 3.13.0 GomSpace · 2020-03-26
  6. SatNOGS DB Libre Space Foundation (SatNOGS Wiki) · 2026-10-18
  7. UHF Transceiver II (product page) EnduroSat · 2026-10-18
  8. SatNOGS-COMMS (project page) Libre Space Foundation · 2026-10-18
  9. Finalizing the CCSDS Space-Data Link Layer Security Protocol: Setup and Execution of the Interoperability Testing ESA, CNES, NASA, DLR, Lockheed Martin (via NASA Technical Reports Server) · 2015-11-01
  10. Satellite security lags decades behind the state of the art Ruhr-Universität Bochum · 2023-07-11
  11. Wireless Signal Injection Attacks on VSAT Satellite Modems USENIX Security Symposium 2024 (ETH Zurich, Ruhr University Bochum, armasuisse Cyber-Defence Campus) · 2024-08-14
  12. Applying the Cybersecurity Framework to Satellite Command and Control: NIST IR 8401 NIST Computer Security Resource Center · 2023-01-03
  13. SPARTA: Space Attack Research and Tactic Analysis - Fact Sheet The Aerospace Corporation · 2023-04-13

Researched and written by the R3KONX analysis desk from the cited primary material. Methodological caveat: the in-orbit exposure figure is the researchers' passive inference from public telemetry, rests on assumed firmware and ground-station configurations, and has not been independently verified; vendor product pages were read as of 18 October 2026 and may describe newer hardware generations than those tested. Corrections to event@r3konx.asia.

R3KONX 2027

Work in this domain? So does the programme

4–6 May 2027, World Trade Centre Kuala Lumpur. Curated talks, hands-on training and The BattleGrid.