CVE-2025-62514 `libparsec_crypto` does not check for weak order point of curve 25519
Man-in-the-middle attackers can bypass SAS verification in Parsec web by exploiting weak Curve25519 points, allowing them to read shared data.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2025-62514?
CVE-2025-62514 is a high-severity vulnerability in Scille parsec-cloud, published on 29 Jan 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Official description
Parsec is a cloud-based application for cryptographically secure file sharing. In versions on the 3.x branch prior to 3.6.0, `libparsec_crypto`, a component of the Parsec application, does not check for weak order point of Curve25519 when compiled with its RustCrypto backend. In practice this means an attacker in a man-in-the-middle position would be able to provide weak order points to both parties in the Diffie-Hellman exchange, resulting in a high probability to for both parties to obtain the same shared key (hence leading to a successful SAS code exchange, misleading both parties into thinking no MITM has occurred) which is also known by the attacker. Note only Parsec web is impacted (as Parsec desktop uses `libparsec_crypto` with the libsodium backend). Version 3.6.0 of Parsec patches the issue.
Which versions are affected by CVE-2025-62514?
It affects 1 product.
Products include Parsec.cloud Parsec.
How do I fix CVE-2025-62514?
No fix has been published for CVE-2025-62514 yet. Limit exposure of the affected software until one is available.
Is CVE-2025-62514 being exploited?
There is no known exploitation of CVE-2025-62514 in the wild and no public exploit code.
Sources
Also known as GHSA-hrc9-gm58-pgj9.