Findings

CVE-2025-13912

Multiple constant-time implementations in wolfSSL before version 5.8.4 may be transformed into non-constant-time binary by LLVM optimizations, which can potentially re…

Published Dec 11, 2025 · updated Oct 14, 2026

Multiple constant-time implementations in wolfSSL before version 5.8.4 may be transformed into non-constant-time binary by LLVM optimizations, which can potentially result in observable timing discrepancies and lead to information disclosure through timing side-channel attacks.

Code

The project this record applies to. Exploit listings stay in References.

Timeline

Detection, updates, and resolution for this record.

  1. Dec 11, 2025 · NIST NVD

    Detected

    Multiple constant-time implementations in wolfSSL before version 5.8.4 may be transformed into non-constant-time binary by LLVM optimizations, which can potentially result in observable timing discrepancies and lead to information disclosure through timing side-channel attacks.

  2. Oct 14, 2026 · NIST NVD

    Updated

    Multiple constant-time implementations in wolfSSL before version 5.8.4 may be transformed into non-constant-time binary by LLVM optimizations, which can potentially result in observable timing discrepancies and lead to information disclosure through timing side-channel attacks.

Sources

  • CVE.orgVulnerability recordCVE-2025-13912

    Official CVE identifier

    cve.org
  • FIRST EPSSExploitation probabilityCVE-2025-13912

    30-day exploitation probability 0.1%

    first.org
  • NIST NVDVulnerability recordCVE-2025-13912

    Multiple constant-time implementations in wolfSSL before version 5.8.4 may be transformed into non-constant-time binary by LLVM optimizations, which can potentially result in observable timing discrepancies and lead to information disclosure through timing side-channel attacks.

    nvd.nist.gov

References

CVE-2025-13912 · ZeroDay Findings