# CVE-2025-61043: Information disclosure in n/a

> An out-of-bounds read in Monkey's Audio allows attackers to crash the application or expose sensitive memory data via crafted UTF-8 strings.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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:** No
- **Published:** 28 Oct 2025
- **Updated:** 29 Oct 2025
- **Also known as:** GHSA-h44j-8jg7-f8wg

## What is CVE-2025-61043?

CVE-2025-61043 is a critical vulnerability in n/a, published on 28 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An out-of-bounds read vulnerability has been discovered in Monkey's Audio 11.31, specifically in the CAPECharacterHelper::GetUTF16FromUTF8 function. The issue arises from improper handling of the length of the input UTF-8 string, causing the function to read past the memory boundary. This vulnerability may result in a crash or expose sensitive data.

Weakness: CWE-125 (Out-of-bounds Read)

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


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

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

## Is CVE-2025-61043 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-61043 is a critical vulnerability in n/a, published on 28 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-61043 exists.

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

## Sources

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

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