CVE-2025-34297

HIGHPre-NVD 8.68.6
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.6 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 94% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Elevated
8.6EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.6Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

KissFFT versions prior to the fix commit 1b083165 contain an integer overflow in kiss_fft_alloc() in kiss_fft.c on platforms where size_t is 32-bit. The nfft parameter is not validated before being used in a size calculation (sizeof(kiss_fft_cpx) * (nfft - 1)), which can wrap to a small value when nfft is large. As a result, malloc() allocates an undersized buffer and the subsequent twiddle-factor initialization loop writes nfft elements, causing a heap buffer overflow. This vulnerability only affects 32-bit architectures.

CVSS v3
8.6
EG Score
8.6(medium)
EG Risk
55(Track*)
EG Risk 55/100SSVC: Track*

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity86% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Watch closely — could escalate to Attend.
EPSS PROB
0%
EPSS %ILE
6%
KEV
Not listed

Published

December 1, 2025

Last Modified

July 14, 2026

Advisory Details (3)

Auto-updated Jul 14, 2026
Upstream fix merged — awaiting tagged release. Sources: github_commit.
generic

KissFFT Integer Overflow Heap Buffer Overflow via kiss_fft_alloc | Advisories | VulnCheck

https://www.vulncheck.com/advisories/kissfft-integer-overflow-heap-buffer-overflow
generic

KissFFT Allocation Function Integer Overflow on 32-bit Systems · Issue #120 · mborgerding/kissfft · GitHub

https://github.com/mborgerding/kissfft/issues/120
github_commit

commit 1b0831658204 (mborgerding/kissfft)

Fix landed in mborgerding/kissfft commit 1b0831658204 — awaiting tagged release

https://github.com/mborgerding/kissfft/commit/1b08316582049c3716154caefc0deab8758506e3

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
kissfft131.1.0-1131.1.0-1+deb11u1
Debian:12(1)
PackageVulnerable rangeFixed inDependents
kissfft131.1.0-3, 131.1.0-4131.1.0-4.1~deb12u1
Debian:13(1)
PackageVulnerable rangeFixed inDependents
kissfft131.1.0-3, 131.1.0-4, 131.1.0-4.1~deb12u1131.1.0-4.1~deb13u1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
kissfft131.1.0-3, 131.1.0-4, 131.1.0-4.1~deb12u1, 131.1.0-4.1~deb13u1131.1.0-4.1

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(1)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 5× in last 7d / 25× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 179 total refreshes for this CVE.

  1. 2026-09-20 20:15 UTCEPSS rescore
  2. 2026-09-18 19:27 UTCEPSS rescore
  3. 2026-09-17 19:29 UTCEPSS rescore
  4. 2026-09-16 14:07 UTCEPSS rescore
  5. 2026-09-16 05:14 UTCEPSS rescore
  6. 2026-09-13 16:46 UTCEPSS rescore
  7. 2026-09-12 15:00 UTCEPSS rescore
  8. 2026-09-12 08:53 UTCOSV refresh
  9. 2026-09-11 14:52 UTCEPSS rescore
  10. 2026-09-11 09:35 UTCEPSS rescore
  11. 2026-09-10 09:33 UTCEPSS rescore
  12. 2026-09-08 21:59 UTCEPSS rescore
  13. 2026-09-07 16:00 UTCEPSS rescore
  14. 2026-09-06 13:46 UTCEPSS rescore
  15. 2026-09-04 05:05 UTCEPSS rescore
  16. 2026-09-01 13:53 UTCEPSS rescore
  17. 2026-09-01 04:38 UTCEPSS rescore
  18. 2026-08-30 19:16 UTCEPSS rescore
  19. 2026-08-30 01:21 UTCEPSS rescore
  20. 2026-08-28 21:40 UTCEPSS rescore
  21. 2026-08-27 14:24 UTCEPSS rescore
  22. 2026-08-26 14:45 UTCEPSS rescore
  23. 2026-08-25 13:48 UTCEPSS rescore
  24. 2026-08-24 14:02 UTCOSV refresh
  25. 2026-08-23 00:18 UTCEPSS rescore
Show 75 more
  1. 2026-08-21 23:48 UTCEPSS rescore
  2. 2026-08-20 22:54 UTCEPSS rescore
  3. 2026-08-19 17:03 UTCEPSS rescore
  4. 2026-08-19 17:03 UTCEPSS rescore
  5. 2026-08-18 13:47 UTCEPSS rescore
  6. 2026-08-17 13:46 UTCEPSS rescore
  7. 2026-08-16 14:55 UTCEPSS rescore
  8. 2026-08-16 02:13 UTCEPSS rescore
  9. 2026-08-15 01:29 UTCEPSS rescore
  10. 2026-08-13 21:59 UTCEPSS rescore
  11. 2026-08-12 13:50 UTCEPSS rescore
  12. 2026-08-09 13:46 UTCEPSS rescore
  13. 2026-08-08 16:36 UTCEPSS rescore
  14. 2026-08-08 09:01 UTCEG score recompute
  15. 2026-08-08 09:01 UTCVendor advisory
  16. 2026-08-08 09:01 UTCGHSA enrichment
  17. 2026-08-07 16:26 UTCEPSS rescore
  18. 2026-08-06 13:46 UTCEPSS rescore
  19. 2026-08-04 15:09 UTCEPSS rescore
  20. 2026-08-04 10:37 UTCEPSS rescore
  21. 2026-08-03 10:35 UTCEPSS rescore
  22. 2026-08-02 02:26 UTCEPSS rescore
  23. 2026-08-01 04:15 UTCEPSS rescore
  24. 2026-07-31 22:12 UTCOSV refresh
  25. 2026-07-30 16:27 UTCEPSS rescore
  26. 2026-07-30 01:29 UTCEPSS rescore
  27. 2026-07-26 14:54 UTCEPSS rescore
  28. 2026-07-25 14:17 UTCEPSS rescore
  29. 2026-07-25 14:17 UTCEPSS rescore
  30. 2026-07-24 14:17 UTCEPSS rescore
  31. 2026-07-23 02:54 UTCEG score recompute
  32. 2026-07-22 14:07 UTCEPSS rescore
  33. 2026-07-22 14:07 UTCEPSS rescore
  34. 2026-07-21 15:24 UTCEPSS rescore
  35. 2026-07-20 17:07 UTCEPSS rescore
  36. 2026-07-19 14:30 UTCEPSS rescore
  37. 2026-07-19 14:30 UTCEPSS rescore
  38. 2026-07-18 10:04 UTCEPSS rescore
  39. 2026-07-18 10:04 UTCEPSS rescore
  40. 2026-07-16 17:02 UTCEPSS rescore
  41. 2026-07-15 16:57 UTCEPSS rescore
  42. 2026-07-15 16:57 UTCEPSS rescore
  43. 2026-07-15 01:59 UTCEPSS rescore
  44. 2026-07-15 01:59 UTCEPSS rescore
  45. 2026-07-14 05:25 UTCOSV refresh
  46. 2026-07-13 22:29 UTCEPSS rescore
  47. 2026-07-13 22:29 UTCEPSS rescore
  48. 2026-07-13 06:12 UTCEPSS rescore
  49. 2026-07-12 05:46 UTCEPSS rescore
  50. 2026-07-11 08:27 UTCEPSS rescore
  51. 2026-07-11 08:27 UTCEPSS rescore
  52. 2026-07-09 19:09 UTCEPSS rescore
  53. 2026-07-09 19:09 UTCEPSS rescore
  54. 2026-07-07 13:45 UTCEPSS rescore
  55. 2026-07-06 02:23 UTCEPSS rescore
  56. 2026-07-05 02:30 UTCEPSS rescore
  57. 2026-07-04 06:30 UTCEPSS rescore
  58. 2026-07-01 15:06 UTCEPSS rescore
  59. 2026-07-01 15:06 UTCEPSS rescore
  60. 2026-06-30 23:22 UTCEPSS rescore
  61. 2026-06-30 23:22 UTCEPSS rescore
  62. 2026-06-29 14:06 UTCEPSS rescore
  63. 2026-06-29 14:06 UTCEPSS rescore
  64. 2026-06-28 14:07 UTCEPSS rescore
  65. 2026-06-28 14:07 UTCEPSS rescore
  66. 2026-06-28 04:55 UTCEPSS rescore
  67. 2026-06-28 04:55 UTCEPSS rescore
  68. 2026-06-27 03:08 UTCEPSS rescore
  69. 2026-06-27 03:08 UTCEPSS rescore
  70. 2026-06-26 02:46 UTCOSV refresh
  71. 2026-06-25 13:49 UTCEPSS rescore
  72. 2026-06-25 13:49 UTCEPSS rescore
  73. 2026-06-24 14:04 UTCEPSS rescore
  74. 2026-06-24 14:04 UTCEPSS rescore
  75. 2026-06-23 21:32 UTCEPSS rescore

Frequently asked(5)

What is CVE-2025-34297?
CVE-2025-34297 is a high vulnerability published on December 1, 2025. KissFFT versions prior to the fix commit 1b083165 contain an integer overflow in kissfftalloc() in kissfft.c on platforms where sizet is 32-bit. The nfft parameter is not validated before being used in a size calculation (sizeof(kissfftcpx) * (nfft - 1)), which can wrap to a small value when nfft…
When was CVE-2025-34297 disclosed?
CVE-2025-34297 was first published in the National Vulnerability Database on December 1, 2025, with the most recent update on July 14, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-34297 actively exploited?
CVE-2025-34297 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 93.8% of all scored CVEs.
What is the CVSS score of CVE-2025-34297?
CVE-2025-34297 has a CVSS v3 base score of 8.6 (NVD).
How do I remediate CVE-2025-34297?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-34297, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2025-34297

Explore →

Is Your Infrastructure Affected by CVE-2025-34297?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.