Radicle disclosed two critical flaws in the network protocol used by its peer-to-peer code-collaboration nodes and warned that every version released so far is affected. The central risk is not forged code: Radicle says signed references still protect repository contents and identities. The concern is exposure of private repositories while they move between nodes.
Radicle disclosed critical network-protocol flaws affecting all released versions of its peer-to-peer code-collaboration software.
The first flaw leaves traffic after the Noise handshake unencrypted and unauthenticated. Repository IDs, peer addresses, gossip and Git objects—including private-repository data—can therefore be read by anyone observing the network path. A second researcher report confirms that this affects every release through 1.10.3 and that no patched version has been released.
The disclosure says repository data can be exposed in transit and that no patched release is available through version 1.10.3.
The second flaw breaks peer authentication during the connection handshake, allowing an attacker to present a Node ID that is not its own. On its own, exploitation still requires knowing an allow-listed ID. The risks compound when a path observer first reads both endpoints’ IDs and later impersonates one to request a private repository directly.
Radicle’s recommended response is to stop using and seeding private repositories over the network until the security update ships. It says to treat previously transmitted private repositories as leaked, rotate any credentials or tokens they contained, and ask authorized peers to block those repositories too. The disclosure also warns that VPNs and similar overlays do not address the separate impersonation flaw.
The eventual fix will replace the current transport with iroh, making it wire-incompatible and requiring a major release. That creates an operational tradeoff: upgrading can separate v2 nodes from v1 peers, but remaining on an affected release leaves private data exposed. No release date or independently supplied technical audit is available, so the timing and completeness of the remediation remain unresolved.