Radicle tells users to stop networking private repositories after transport flaws

Radicle has disclosed two critical flaws in the network protocol used by its peer-to-peer code collaboration system and says every version released so far is affected. Node traffic is sent without the confidentiality Radicle expected, so anyone able to observe the path between two nodes can read the objects they exchange. The project says signed references still verify repository contents, which limits the impact to confidentiality rather than allowing an observer to forge code or identities.

The risk is most serious for private repositories. Radicle says users should stop sharing them over the network until a fixed release is available and should treat any private repository already transmitted between nodes as potentially disclosed. If those repositories contained unencrypted credentials, keys or tokens, the project advises rotating them.

A separate handshake flaw allows a connecting peer to present a Node ID it does not own. Private repositories are shared only with allow-listed Node IDs, so an attacker who learns an allowed identifier can impersonate it and fetch the repository. On its own, that attack requires knowledge of an allow-listed ID. In combination with the cleartext transport flaw, an observer on the network path can learn the IDs used by both endpoints and then use one to request the full private repository.

Konstantinos Maninakis, who reported the cleartext issue in June, published packet-capture evidence from current Radicle software. He describes a clone performed against a Radicle 1.10.3 node in which Git request and response data, including packfile contents, could be read directly from the captured stream. Radicle says its team independently reproduced the cleartext repository transfer after receiving his report.

There is no compatible patch for the existing wire protocol. Radicle says the repair will arrive as a breaking major release built around iroh, replacing the current custom networking layer. Until then, the project recommends blocking private repositories from seeding or stopping the node. It also warns that adding Tor, I2P or a VPN does not fix the peer-impersonation flaw, even if an encrypted overlay reduces who can observe the transport path.

The disclosure does not establish that the flaws were exploited against users. It establishes that confidentiality and peer authentication were absent where Radicle expected them to exist, and that exposure already incurred cannot be reversed by a later update. Public repositories have a different risk profile because their contents are already intended to be shared, while private-repository users face the possibility that network observers or impersonating peers could have obtained material meant to remain restricted.