Skip to main content
CVE-2025-7844VulnerabilityPublished

CVE-2025-7844: wolfSSL wolfTPM · CWE-121

Affects wolfSSL wolfTPMSource CVE Database V5

0

Not known to be exploited · CVSS 1.0 Low.

Data as of 26 Oct 2026, 07:57 UTC

CVSS 4.0 base score
1.0Low
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 4% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:P/AC:H/AT:P/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:L/U:Green

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 4 Aug 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

What to do

Affected software

ProductAffectedFixed in
wolfSSL Inc. wolfTPMAffected
  • =0
Fixed in–

AI-suggested

To mitigate this vulnerability, European organizations should: 1) Review and verify the build-time configuration of wolfTPM, ensuring that the MAX_RSA_KEY_BITS macro is set to match the maximum RSA key size supported by their TPM 2.0 hardware. This prevents buffer overruns by allocating sufficient stack space. 2) Audit applications that use wolfTPM to confirm they do not create or import RSA keys larger than 2048 bits unless the build configuration supports it. 3) Implement strict code review and testing procedures for cryptographic modules to detect and prevent buffer overflow conditions. 4) Monitor vendor communications for patches or updates from wolfSSL Inc. and apply them promptly once available. 5) Limit local access to systems running vulnerable wolfTPM versions to trusted personnel only, reducing the risk of exploitation. 6) Employ runtime protections such as stack canaries, address space layout randomization (ASLR), and control flow integrity (CFI) to mitigate the impact of potential buffer overflows. 7) Consider using alternative TPM middleware or updated wolfTPM versions that explicitly address this vulnerability if available.

Description

Exporting a TPM based RSA key larger than 2048 bits from the TPM could overrun a stack buffer if the default `MAX_RSA_KEY_BITS=2048` is used. If your TPM 2.0 module supports RSA key sizes larger than 2048 bit and your applications supports creating or importing an RSA private or public key larger than 2048 bits and your application calls `wolfTPM2_RsaKey_TpmToWolf` on that key, then a stack buffer could be overrun. If the `MAX_RSA_KEY_BITS` build-time macro is set correctly (RSA bits match what TPM hardware is capable of) for the hardware target, then a stack overrun is not possible.

References

Community reviews

Loading reviews…