Analysis and contextual insights are available on OpenCVE Cloud.
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
No advisories yet.
Mon, 02 Mar 2026 18:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Parsec.cloud
Parsec.cloud parsec |
|
| CPEs | cpe:2.3:a:parsec.cloud:parsec:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Parsec.cloud
Parsec.cloud parsec |
Fri, 30 Jan 2026 09:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Scille
Scille parsec-cloud |
|
| Vendors & Products |
Scille
Scille parsec-cloud |
Thu, 29 Jan 2026 22:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Thu, 29 Jan 2026 16:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | `libparsec_crypto` does not check for weak order point of curve 25519 | |
| Weaknesses | CWE-1240 CWE-327 |
|
| References |
|
|
| Metrics |
cvssV3_1
|
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2026-01-29T21:29:03.456Z
Reserved: 2025-10-15T15:03:28.134Z
Link: CVE-2025-62514
Updated: 2026-01-29T21:28:58.803Z
Status : Analyzed
Published: 2026-01-29T16:16:09.387
Modified: 2026-03-02T18:34:13.947
Link: CVE-2025-62514
No data.
OpenCVE Enrichment
Updated: 2026-01-30T08:43:18Z