Use of a Broken or Risky Cryptographic Algorithm Affecting libtpms package, versions <0.10.2-1


Severity

Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.01% (1st percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications

Snyk Learn

Learn about Use of a Broken or Risky Cryptographic Algorithm vulnerabilities in an interactive lesson.

Start learning
  • Snyk IDSNYK-DEBIANUNSTABLE-LIBTPMS-14849504
  • published3 Jan 2026
  • disclosed2 Jan 2026

Introduced: 2 Jan 2026

CVE-2026-21444  (opens in a new tab)
CWE-327  (opens in a new tab)
CWE-330  (opens in a new tab)

How to fix?

Upgrade Debian:unstable libtpms to version 0.10.2-1 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream libtpms package and not the libtpms package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

libtpms, a library that provides software emulation of a Trusted Platform Module, has a flaw in versions 0.10.0 and 0.10.1. The commonly used integration of libtpms with OpenSSL 3.x contained a vulnerability related to the returned IV (initialization vector) when certain symmetric ciphers were used. Instead of returning the last IV it returned the initial IV to the caller, thus weakening the subsequent encryption and decryption steps. The highest threat from this vulnerability is to data confidentiality. Version 0.10.2 fixes the issue. No known workarounds are available.

CVSS Base Scores

version 3.1