# CVE-2026-41445: KissFFT Integer Overflow Heap Buffer Overflow via kiss_fftndr_alloc()

> Attackers can trigger heap buffer overflow via integer overflow in KissFFT, potentially leading to code execution or denial of service.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 20 Apr 2026
- **Updated:** 14 Jul 2026
- **Also known as:** DEBIAN-CVE-2026-41445, GHSA-xpr7-5899-f5vj, UBUNTU-CVE-2026-41445, openSUSE-SU-2026:10591-1

## What is CVE-2026-41445?

CVE-2026-41445 is a high-severity vulnerability in mborgerding kissfft, published on 20 Apr 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

KissFFT before commit 8a8e66e contains an integer overflow vulnerability in the kiss_fftndr_alloc() function in kiss_fftndr.c where the allocation size calculation dimOther*(dimReal+2)*sizeof(kiss_fft_scalar) overflows signed 32-bit integer arithmetic before being widened to size_t, causing malloc() to allocate an undersized buffer. Attackers can trigger heap buffer overflow by providing crafted dimensions that cause the multiplication to exceed INT_MAX, allowing writes beyond the allocated buffer region when kiss_fftndr() processes the data.

Weakness: CWE-190 (Integer Overflow or Wraparound), CWE-122 (Heap-based Buffer Overflow)

## Which versions are affected by CVE-2026-41445?


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `kissfft` | openSUSE:Tumbleweed | All versions | 131.2.0-2.1 |

## How do I fix CVE-2026-41445?

Apply the vendor's patch.

## Is CVE-2026-41445 being exploited?

There is no known exploitation of CVE-2026-41445 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-41445 and fix it if it is affected.

What it is: CVE-2026-41445 is a high-severity vulnerability in mborgerding kissfft, published on 20 Apr 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-41445 in the wild and no public exploit code.

Affected product: mborgerding kissfft. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-41445/ (Markdown: https://insights.sbomify.com/CVE-2026-41445/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-41445
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-41445
- OSV: https://osv.dev/vulnerability/CVE-2026-41445

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-41445/
Summaries are generated and may contain mistakes; the official description above is the record.