# CVE-2024-58262: curve25519-dalek has timing variability in `curve25519-dalek`'s `Scalar29::sub`/`Scalar52::sub`

> Attackers may exploit timing side-channels in elliptic curve operations due to compiler optimizations removing constant-time guarantees, potentially leaking secret keys.

- **Severity:** Low 2.9 (`CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 27 Jul 2025
- **Updated:** 28 Jul 2025
- **Also known as:** DEBIAN-CVE-2024-58262, GHSA-x4gp-pqpj-f43q, RUSTSEC-2024-0344

## What is CVE-2024-58262?

CVE-2024-58262 is a low-severity vulnerability in dalek-cryptography curve25519-dalek, published on 27 Jul 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The curve25519-dalek crate before 4.1.3 for Rust has a constant-time operation on elliptic curve scalars that is removed by LLVM.

Weakness: CWE-733 (Compiler Optimization Removal or Modification of Security-critical Code)

## Which versions are affected by CVE-2024-58262?

3 open source packages ship an affected version, including curve25519-dalek. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `curve25519-dalek` | crates.io | All versions | 4.1.3 |
| `curve25519-dalek` | crates.io | All versions | 4.1.3 |
| `curve25519-dalek` | crates.io | From 0.0.0-0 | 4.1.3 |

Products: Dalek Curve25519-Dalek.

## How do I fix CVE-2024-58262?

Upgrade curve25519-dalek to 4.1.3 or later.

## Is CVE-2024-58262 being exploited?

There is no known exploitation of CVE-2024-58262 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-58262 and fix it if it is affected.

What it is: CVE-2024-58262 is a low-severity vulnerability in dalek-cryptography curve25519-dalek, published on 27 Jul 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-58262 in the wild and no public exploit code.

Affected packages and fixed versions:
- curve25519-dalek (crates.io): affected all versions; fixed in 4.1.3
- curve25519-dalek (crates.io): affected all versions; fixed in 4.1.3
- curve25519-dalek (crates.io): affected from 0.0.0-0; fixed in 4.1.3

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-2024-58262/ (Markdown: https://insights.sbomify.com/CVE-2024-58262/index.md)
```

## Sources

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

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