How severe is CVE-2026-21444?

CVE-2026-21444 has a CVSS 3.x base score of 5.5, rated medium severity. It is exploitable over local access with low attack complexity, requires low privileges and no user interaction. Impact on confidentiality is high, integrity none, and availability none.

Is CVE-2026-21444 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (1st percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2026-21444?

CVE-2026-21444 affects Libtpms Project Libtpms. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2026-21444?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.

Does CVE-2026-21444 have an EU (EUVD) identifier?

Yes. CVE-2026-21444 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2026-0753.

When was CVE-2026-21444 published?

CVE-2026-21444 was published on 2026-01-02 and last updated on 2026-06-17.

CVE-2026-21444

CVE-2026-21444 is a medium-severity vulnerability in Libtpms Project Libtpms with a CVSS 3.x base score of 5.5. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-327.

Key facts

Severity: Medium (CVSS 3.x base score 5.5)
EPSS exploit prediction: 0% (1st percentile)
Actively exploited: Not listed in CISA KEV
EU (EUVD) id: EUVD-2026-0753
Weakness: CWE-327
Affected product: Libtpms Project Libtpms
Published: 2026-01-02
Last modified: 2026-06-17

Description

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.

Frequently asked questions

What is CVE-2026-21444?: 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.
How severe is CVE-2026-21444?: CVE-2026-21444 has a CVSS 3.x base score of 5.5, rated medium severity. It is exploitable over local access with low attack complexity, requires low privileges and no user interaction. Impact on confidentiality is high, integrity none, and availability none.
Is CVE-2026-21444 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (1st percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2026-21444?: CVE-2026-21444 affects Libtpms Project Libtpms. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2026-21444?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
Does CVE-2026-21444 have an EU (EUVD) identifier?: Yes. CVE-2026-21444 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2026-0753.
When was CVE-2026-21444 published?: CVE-2026-21444 was published on 2026-01-02 and last updated on 2026-06-17.

References

Affected products (1)

cpe:2.3:a:libtpms_project:libtpms:*:*:*:*:*:*:*:*

More vulnerabilities in Libtpms Project Libtpms

CVE-2021-3746 — Medium (CVSS 6.5): A flaw was found in the libtpms code that may cause access beyond the boundary of internal buffers. The vulnerability…
CVE-2021-3623 — Medium (CVSS 6.1): A flaw was found in libtpms. The flaw can be triggered by specially-crafted TPM 2 command packets containing illegal…
CVE-2025-49133 — Medium (CVSS 5.9): Libtpms is a library that targets the integration of TPM functionality into hypervisors, primarily into Qemu. Libtpms,…
CVE-2021-3569 — Medium (CVSS 5.5): A stack corruption bug was found in libtpms in versions before 0.7.2 and before 0.8.0 while decrypting data using RSA.…
CVE-2021-3505 — Medium (CVSS 5.5): A flaw was found in libtpms in versions before 0.8.0. The TPM 2 implementation returns 2048 bit keys with ~1984 bit…
CVE-2021-3446 — Medium (CVSS 5.5): A flaw was found in libtpms in versions before 0.8.2. The commonly used integration of libtpms with OpenSSL contained a…

All CVEs affecting Libtpms Project Libtpms →

Other CWE-327 (Use of a Broken or Risky Cryptographic Algorithm) vulnerabilities

CVE-2026-50086 — Critical (CVSS 10.0): The Aqara IAM/SSO gateway (gw-builder.aqara.com) exposes bidirectional AES round-trups against the platform's signing…
CVE-2026-21718 — Critical (CVSS 10.0): An authentication bypass vulnerability exists in Copeland XWEB Pro version 1.12.1 and prior, enabling any attackers to…
CVE-2025-54426 — Critical (CVSS 9.9): Polkadot Frontier is an Ethereum and EVM compatibility layer for Polkadot and Substrate. In versions prior to commit…
CVE-2024-51478 — Critical (CVSS 9.9): YesWiki is a wiki system written in PHP. Prior to 4.4.5, the use of a weak cryptographic algorithm and a hard-coded…
CVE-2026-28252 — Critical (CVSS 9.8): A Use of a Broken or Risky Cryptographic Algorithm vulnerability in Trane Tracer SC, Tracer SC+, and Tracer Concierge…
CVE-2025-13476 — Critical (CVSS 9.8): Rakuten Viber Cloak mode in Android v25.7.2.0g and Windows v25.6.0.0–v25.8.1.0 uses a static and predictable TLS…

Browse all CWE-327 (Use of a Broken or Risky Cryptographic Algorithm) vulnerabilities →