CVE-2019-25003: An issue was discovered in the libsecp256k1 crate before 0.3.1 for Rust

Q: How do I fix CVE-2019-25003?

libsecp256k1: upgrade to 0.3.1. Exact commands for each OS are on this page.

Q: Is CVE-2019-25003 being exploited?

CVE-2019-25003 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2019-25003 affect?

CVE-2019-25003 affects libsecp256k1. Severity is high (CVSS 7.5). An issue was discovered in the libsecp256k1 crate before 0.3.1 for Rust. Scalar::check_overflow allows a timing side-channel attack; consequently, attackers can obtain sensitive information.

Q: How urgent is CVE-2019-25003?

Priority 51/100. High severity; Remotely exploitable, no login, no user action

This month

HIGH 7.5REMOTEUPGRADE

CVE-2019-25003 is a high-severity flaw (CVSS 7.5) affecting libsecp256k1. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

An issue was discovered in the libsecp256k1 crate before 0.3.1 for Rust. Scalar::check_overflow allows a timing side-channel attack; consequently, attackers can obtain sensitive information.

Why this priority

High severity
Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	7.5 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	1.7% (top 23%)
CISA exploited list	No
Published	2020-12-31
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: parity

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2020-12-31 10:15 UTCPublished CVE record published
2026-06-17 02:31 UTCUpdated Record last modified

parity libsecp256k1 UPGRADE

Affected: < 0.3.1

Fixed in: 0.3.1

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy libsecp256k1 || rpm -q libsecp256k1 || libsecp256k1 --version

2. UPGRADE to 0.3.1 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade libsecp256k1

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade libsecp256k1

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2019-25003?

libsecp256k1: upgrade to 0.3.1. Exact commands for each OS are on this page.

Is CVE-2019-25003 being exploited?

CVE-2019-25003 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2019-25003 affect?

CVE-2019-25003 affects libsecp256k1. Severity is high (CVSS 7.5). An issue was discovered in the libsecp256k1 crate before 0.3.1 for Rust. Scalar::check_overflow allows a timing side-channel attack; consequently, attackers can obtain sensitive information.

How urgent is CVE-2019-25003?

Priority 51/100. High severity; Remotely exploitable, no login, no user action

Related CVEs

CVE-2021-38195 CRITICAL 9.8 UPGRADE An issue was discovered in the libsecp256k1 crate before 0.5.0 for Rust
CVE-2019-20399 MEDIUM 5.9 UPGRADE A timing vulnerability in the Scalar::check_overflow function in Parity libsecp256k1-rs before 0.3.1 potential

References

← Back to latest CVEs