# CVE-2025-6271: swftools wav2swf wav.c wav_convert2mono out-of-bounds

> A local attacker can trigger an out-of-bounds read in swftools wav2swf, potentially causing a crash or leaking memory.

- **Severity:** Medium 4.8 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Jun 2025
- **Updated:** 23 Jun 2025
- **Also known as:** GHSA-83f6-rpg2-3v27, UBUNTU-CVE-2025-6271

## What is CVE-2025-6271?

CVE-2025-6271 is a medium-severity memory corruption vulnerability in Swftools Swftools, published on 19 Jun 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability, which was classified as problematic, was found in swftools up to 0.9.2. This affects the function wav_convert2mono in the library lib/wav.c of the component wav2swf. The manipulation leads to out-of-bounds read. The attack needs to be approached locally. The exploit has been disclosed to the public and may be used.

Weakness: CWE-125 (Out-of-bounds Read), CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

## Which versions are affected by CVE-2025-6271?

It affects 1 product.


Products: Swftools Swftools.

## How do I fix CVE-2025-6271?

No fix has been published for CVE-2025-6271 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-6271 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-6271 exists.

## Other vulnerabilities in Swftools Swftools

- [CVE-2022-40008](https://insights.sbomify.com/CVE-2022-40008/): Memory corruption in n/a (critical 9.8)
- [CVE-2022-40009](https://insights.sbomify.com/CVE-2022-40009/): Use after free in n/a (critical 9.8)
- [CVE-2010-1516](https://insights.sbomify.com/CVE-2010-1516/): Integer overflow in n/a (critical 9.3)
- [CVE-2024-26339](https://insights.sbomify.com/CVE-2024-26339/): Memory corruption in n/a (critical 9.1)
- [CVE-2024-25165](https://insights.sbomify.com/CVE-2024-25165/): Memory corruption in n/a (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-6271 and fix it if it is affected.

What it is: CVE-2025-6271 is a medium-severity memory corruption vulnerability in Swftools Swftools, published on 19 Jun 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-6271 exists.

Affected product: Swftools Swftools. 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-2025-6271/ (Markdown: https://insights.sbomify.com/CVE-2025-6271/index.md)
```

## Sources

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

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