# CVE-2026-37555: Integer overflow in n/a

> An integer overflow in libsndfile's WAV IMA ADPCM codec allows attackers to cause heap buffer overflows or denial of service via crafted files.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 29 Apr 2026
- **Updated:** 15 Jul 2026
- **Also known as:** ALSA-2026:19559, ALSA-2026:19560, ALSA-2026:19610, AZL-85457, CLSA-2026-1780515309, CLSA-2026-1780592196, DEBIAN-CVE-2026-37555, ECHO-784a-04f4-95b4, GHSA-x46m-7mvp-6fvq, OESA-2026-2711, OESA-2026-2712, RHSA-2026:19559, RHSA-2026:19560, RHSA-2026:19610, RHSA-2026:23221, RHSA-2026:23222, RHSA-2026:23223, RHSA-2026:25092, RHSA-2026:25197, RHSA-2026:25198, RHSA-2026:25227, RLSA-2026:19559, RLSA-2026:19560, RLSA-2026:19610, ROOT-OS-DEBIAN-12-CVE-2026-37555, ROOT-OS-DEBIAN-13-CVE-2026-37555, UBUNTU-CVE-2026-37555

## What is CVE-2026-37555?

CVE-2026-37555 is a high-severity vulnerability in n/a, published on 29 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered in libsndfile 1.2.2 IMA ADPCM codec. The AIFF code path (line 241) was fixed with (sf_count_t) cast, but the WAV code path (line 235) and close path (line 167) were not. When samplesperblock (int) * blocks (int) exceeds INT_MAX, the 32-bit multiplication overflows before being assigned to sf.frames (sf_count_t/int64). With samplesperblock=50000 and blocks=50000, the product 2500000000 overflows to -1794967296. This causes incorrect frame count leading to heap buffer overflow or denial of service. Both values come from the WAV file header and are attacker-controlled. This issue was discovered after an incomplete fix for CVE-2022-33065.

Weakness: CWE-190 (Integer Overflow or Wraparound)

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

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `libsndfile` | AlmaLinux:10 | All versions | 1.2.2-6.el10_2.1 |
| `libsndfile-devel` | AlmaLinux:10 | All versions | 1.2.2-6.el10_2.1 |
| `libsndfile-utils` | AlmaLinux:10 | All versions | 1.2.2-6.el10_2.1 |
| `libsndfile` | AlmaLinux:8 | All versions | 1.0.28-17.el8_10 |
| `libsndfile-devel` | AlmaLinux:8 | All versions | 1.0.28-17.el8_10 |
| `libsndfile-utils` | AlmaLinux:8 | All versions | 1.0.28-17.el8_10 |
| `libsndfile` | AlmaLinux:9 | All versions | 1.0.31-9.el9_8.1 |
| `libsndfile-devel` | AlmaLinux:9 | All versions | 1.0.31-9.el9_8.1 |
| `libsndfile-utils` | AlmaLinux:9 | All versions | 1.0.31-9.el9_8.1 |
| `libsndfile` | Red Hat:enterprise_linux:10.2 | All versions | 0:1.2.2-6.el10_2.1 |
| `libsndfile-debuginfo` | Red Hat:enterprise_linux:10.2 | All versions | 0:1.2.2-6.el10_2.1 |
| `libsndfile-debugsource` | Red Hat:enterprise_linux:10.2 | All versions | 0:1.2.2-6.el10_2.1 |
| `libsndfile-devel` | Red Hat:enterprise_linux:10.2 | All versions | 0:1.2.2-6.el10_2.1 |
| `libsndfile-utils` | Red Hat:enterprise_linux:10.2 | All versions | 0:1.2.2-6.el10_2.1 |
| `libsndfile-utils-debuginfo` | Red Hat:enterprise_linux:10.2 | All versions | 0:1.2.2-6.el10_2.1 |
| `libsndfile` | Red Hat:enterprise_linux:8::appstream | All versions | 0:1.0.28-17.el8_10 |
| `libsndfile-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 0:1.0.28-17.el8_10 |
| `libsndfile-debugsource` | Red Hat:enterprise_linux:8::appstream | All versions | 0:1.0.28-17.el8_10 |
| `libsndfile-utils` | Red Hat:enterprise_linux:8::appstream | All versions | 0:1.0.28-17.el8_10 |
| `libsndfile-utils-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 0:1.0.28-17.el8_10 |
| `libsndfile-debuginfo` | Red Hat:enterprise_linux:8::crb | All versions | 0:1.0.28-17.el8_10 |
| `libsndfile-debugsource` | Red Hat:enterprise_linux:8::crb | All versions | 0:1.0.28-17.el8_10 |
| `libsndfile-devel` | Red Hat:enterprise_linux:8::crb | All versions | 0:1.0.28-17.el8_10 |
| `libsndfile-utils-debuginfo` | Red Hat:enterprise_linux:8::crb | All versions | 0:1.0.28-17.el8_10 |
| `libsndfile` | Red Hat:enterprise_linux:9::appstream | All versions | 0:1.0.31-9.el9_8.1 |
| `libsndfile-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 0:1.0.31-9.el9_8.1 |
| `libsndfile-debugsource` | Red Hat:enterprise_linux:9::appstream | All versions | 0:1.0.31-9.el9_8.1 |
| `libsndfile-utils` | Red Hat:enterprise_linux:9::appstream | All versions | 0:1.0.31-9.el9_8.1 |
| `libsndfile-utils-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 0:1.0.31-9.el9_8.1 |
| `libsndfile-debuginfo` | Red Hat:enterprise_linux:9::crb | All versions | 0:1.0.31-9.el9_8.1 |
| `libsndfile-debugsource` | Red Hat:enterprise_linux:9::crb | All versions | 0:1.0.31-9.el9_8.1 |
| `libsndfile-devel` | Red Hat:enterprise_linux:9::crb | All versions | 0:1.0.31-9.el9_8.1 |
| `libsndfile-utils-debuginfo` | Red Hat:enterprise_linux:9::crb | All versions | 0:1.0.31-9.el9_8.1 |
| `libsndfile` | Red Hat:enterprise_linux_eus:10.0 | All versions | 0:1.2.2-5.el10_0.1 |
| `libsndfile-debuginfo` | Red Hat:enterprise_linux_eus:10.0 | All versions | 0:1.2.2-5.el10_0.1 |
| `libsndfile-debugsource` | Red Hat:enterprise_linux_eus:10.0 | All versions | 0:1.2.2-5.el10_0.1 |
| `libsndfile-devel` | Red Hat:enterprise_linux_eus:10.0 | All versions | 0:1.2.2-5.el10_0.1 |
| `libsndfile-utils` | Red Hat:enterprise_linux_eus:10.0 | All versions | 0:1.2.2-5.el10_0.1 |
| `libsndfile-utils-debuginfo` | Red Hat:enterprise_linux_eus:10.0 | All versions | 0:1.2.2-5.el10_0.1 |
| `libsndfile` | Red Hat:rhel_aus:8.4::appstream | All versions | 0:1.0.28-10.el8_4.2 |

Products: Libsndfile Project Libsndfile.

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

Apply the vendor's patch.

## Is CVE-2026-37555 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2017-6892](https://insights.sbomify.com/CVE-2017-6892/): Memory corruption in libsndfile (high 8.8)
- [CVE-2022-33064](https://insights.sbomify.com/CVE-2022-33064/): Memory corruption in n/a (high 7.8)
- [CVE-2022-33065](https://insights.sbomify.com/CVE-2022-33065/): Integer overflow in n/a (high 7.8)
- [CVE-2025-52194](https://insights.sbomify.com/CVE-2025-52194/): Memory corruption in n/a (high 7.5)
- [CVE-2024-50613](https://insights.sbomify.com/CVE-2024-50613/): Denial of service in n/a (medium 6.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-37555 is a high-severity vulnerability in n/a, published on 29 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-37555 in the wild and no public exploit code.

Affected product: n/a. 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-37555/ (Markdown: https://insights.sbomify.com/CVE-2026-37555/index.md)
```

## Sources

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

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