Radicle, a decentralized code collaboration network built on peer-to-peer protocols, disclosed the vulnerabilities on September 23, 2026. The defects lie in the radicle-node daemon, which manages peer synchronization. Although Radicle uses the Noise Protocol Framework for connection handshakes, the derived encryption keys are discarded immediately after negotiation. All subsequent communication—including Git object packs, gossip metadata, and routing tables—is sent over the TCP socket in plaintext.
A second authentication flaw allows attackers to forge connections by spoofing a Node ID from an allow-listed peer. Because valid Node IDs are transmitted in cleartext, an on-path eavesdropper can capture them and then impersonate authorized peers to pull private repositories from seed nodes.
The core architectural issue stems from a mismatch between Radicle's transport setup and frame dispatching in the underlying Rust repository, Heartwood. The network state machine processes the Noise handshake during initialization, but the framing layer bypasses encryption routines during write operations. A hex dump of captured traffic confirms that post-handshake frames lack authentication tags or stream ciphers.
Without version negotiation in the protocol design, Radicle maintainers cannot deploy a wire-level fix that remains compatible with existing nodes. They have recommended that users immediately halt all private repository operations over clearnet until a major architectural overhaul is released.