Timing Attack Vulnerability in libsecp256k1

libsecp256k1 Updated 02 Oct 2025

Summary

25/08/2021
Yes i
High
7.5

CVE-2019-25003: libsecp256k1 contains side-channel timing attack. Affects libsecp256k1 versions < 0.3.1. Fixed in 0.3.1. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

libsecp256k1 is a library for efficient elliptic curve operations on the secp256k1 curve, which is used in the Bitcoin and Ethereum cryptocurrencies. It provides functions for key generation, signing, and verification. However, versions prior to 0.3.1 contain a vulnerability that allows for a side-channel timing attack.

Vulnerability Detail

The vulnerability in libsecp256k1 arises from the fact that the Scalar::check_overflow function is not executed in constant time. This means that an attacker can potentially leak information by measuring the timing of the execution. By carefully measuring the time taken for certain operations, an attacker can infer sensitive information such as private keys or other cryptographic secrets. This timing attack can be performed remotely without requiring any special privileges.

How To Fix

Latest published version: 0.7.2 as of 23 Oct 2026

Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.

If you need the minimum change

0.3.1

This is the first release that contains the fix.

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

There is no known workaround for this vulnerability. It is necessary to upgrade to the fixed version of libsecp256k1 to mitigate the risk of a timing attack.

Conclusion

The timing attack vulnerability in libsecp256k1 can potentially lead to the leakage of sensitive information, such as private keys, through a side-channel timing attack. To mitigate this risk, it is crucial to upgrade to version 0.3.1 or later of libsecp256k1. For further assistance and support in vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for libsecp256k1 →

Share this vulnerability

FAQ

libsecp256k1 is a library for efficient elliptic curve operations on the secp256k1 curve, which is used in cryptocurrencies like Bitcoin and Ethereum.

A timing attack is a type of side-channel attack where an attacker measures the time taken by certain operations to infer sensitive information.

The timing attack in libsecp256k1 exploits the fact that the Scalar::check_overflow function is not executed in constant time, allowing an attacker to measure the timing and infer sensitive information.

Yes, the timing attack can be performed remotely without requiring any special privileges.

No, there is no known workaround. It is necessary to upgrade to the fixed version of libsecp256k1.

Related vulnerabilities

Recent vulnerabilities recorded for libsecp256k1.

How To Fix

Latest published version: 0.7.2 as of 23 Oct 2026

Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.

If you need the minimum change

0.3.1

This is the first release that contains the fix.

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback