# CVE-2022-50237: `ed25519-dalek` Double Public Key Signing Function Oracle Attack

> Attackers can extract private keys via a signing oracle attack in the ed25519-dalek Rust library, compromising cryptographic security.

- **Severity:** Medium 5.9 (`CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:C/C:H/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:** 28 Jul 2025
- **Updated:** 28 Jul 2025
- **Also known as:** GHSA-w5vr-6qhr-36cc, HSEC-2025-0002, RUSTSEC-2022-0093, UBUNTU-CVE-2022-50237

## What is CVE-2022-50237?

CVE-2022-50237 is a medium-severity vulnerability in dalek-cryptography ed25519-dalek, published on 28 Jul 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The ed25519-dalek crate before 2 for Rust allows a double public key signing function oracle attack. The Keypair implementation leads to a simple computation for extracting a private key.

Weakness: CWE-497 (Exposure of Sensitive System Information to an Unauthorized Control Sphere)

## Which versions are affected by CVE-2022-50237?

5 open source packages ship an affected version, including ed25519-dalek, crypton and cryptonite.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `ed25519-dalek` | crates.io | All versions | 2.0.0 |
| `ed25519-dalek` | crates.io | All versions | 2.0.0 |
| `ed25519-dalek` | crates.io | From 0.0.0-0 | 2.0.0 |
| `crypton` | Hackage | From 0.31 | 1.0.3 |
| `cryptonite` | Hackage | From 0.1 | None |

## How do I fix CVE-2022-50237?

Upgrade ed25519-dalek to 2.0.0 or later.

## Is CVE-2022-50237 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-50237 and fix it if it is affected.

What it is: CVE-2022-50237 is a medium-severity vulnerability in dalek-cryptography ed25519-dalek, published on 28 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-2022-50237 in the wild and no public exploit code.

Affected packages and fixed versions:
- ed25519-dalek (crates.io): affected all versions; fixed in 2.0.0
- ed25519-dalek (crates.io): affected all versions; fixed in 2.0.0
- ed25519-dalek (crates.io): affected from 0.0.0-0; fixed in 2.0.0
- crypton (Hackage): affected from 0.31; fixed in 1.0.3
- cryptonite (Hackage): affected from 0.1; no fix listed

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

## Sources

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

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