# 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.

- **Severity:** High 8.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Jan 2026
- **Updated:** 29 Jan 2026
- **Also known as:** GHSA-hrc9-gm58-pgj9

## 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.

Weakness: CWE-327 (Use of a Broken or Risky Cryptographic Algorithm), CWE-1240 (Use of a Cryptographic Primitive with a Risky Implementation)

## Which versions are affected by CVE-2025-62514?

It affects 1 product.


Products: 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.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-62514 and fix it if it is affected.

What it is: 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.
Exploitation: There is no known exploitation of CVE-2025-62514 in the wild and no public exploit code.

Affected product: Scille parsec-cloud. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-62514/ (Markdown: https://insights.sbomify.com/CVE-2025-62514/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-62514
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-62514
- OSV: https://osv.dev/vulnerability/CVE-2025-62514

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-62514/
Summaries are generated and may contain mistakes; the official description above is the record.