Skip to content
Fencer Intel
medium 5.3

CVE-2019-16910 json

Arm Mbed TLS before 2.19.0 and Arm Mbed Crypto before 2.0.0, when deterministic ECDSA is enabled,...

published 7y ago modified 3mo ago also EUVD-2019-7407 , JLSEC-2025-198

cvss
5.3
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
1.8%
EPSS 1.8% chance of exploitation in 30 days, percentile 78%
public exploits
0
none known

Summary

Arm Mbed TLS before 2.19.0 and Arm Mbed Crypto before 2.0.0, when deterministic ECDSA is enabled, use an RNG with insufficient entropy for blinding, which might allow an attacker to recover a private key via side-channel attacks if a victim signs the same message many times. (For Mbed TLS, the fix is also available in versions 2.7.12 and 2.16.3.)

Patch / fix

  • julia MbedTLS_jll 2.16.6+0
  • arm mbed_crypto 2.0.0
  • arm mbed_tls 2.7.12, 2.16.3
  • trustedfirmware mbed_tls 2.19.0
  • mbedtls Debian 14, Debian 13, Debian 12 2.16.3-1

debian advisories DEBIAN-CVE-2019-16910

  • mbedtls Alpine 3.24, Alpine 3.23, Alpine 3.22 +12 more 2.16.3-r0
  • mbedtls2 Alpine 3.24, Alpine 3.23, Alpine 3.22 +2 more 2.16.3-r0
  • mbedtls3 Alpine 3.24 2.16.3-r0

alpine advisories ALPINE-CVE-2019-16910

Alpine secdb © Alpine Linux, from https://secdb.alpinelinux.org via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

Is CVE-2019-16910 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2019-16910 updated cvss 5.9

mbedtls: use of RNG with insufficient entropy allows to recover private key vise side-channel attack

  • Red Hat All currently supported Red Hat products
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

1.76% chance of exploitation in the next 30 days, higher than 78% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.1 5.3 CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:N/A:N
NVD 2.0 2.6 AV:N/AC:H/Au:N/C:P/I:N/A:N
OSV 3.1 5.3 CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:N/A:N

Affected packages

ecosystem package affected fixed in
julia MbedTLS_jll
<2.16.6+0
2.16.6+0

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.