# CVE-2025-32106: Code injection in n/a

> Unauthenticated remote attackers can execute unauthorized code on Audiocodes Mediapack devices via crafted POST requests.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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:** 3 Jun 2025
- **Updated:** 18 Jun 2025
- **Also known as:** GHSA-hx7r-89vp-x3gj

## What is CVE-2025-32106?

CVE-2025-32106 is a critical code injection vulnerability in n/a, published on 3 Jun 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In Audiocodes Mediapack MP-11x through 6.60A.369.002, a crafted POST request request may result in an unauthenticated remote user's ability to execute unauthorized code.

Weakness: CWE-94 (Improper Control of Generation of Code)

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

It affects 3 products.


Products: Audiocodes Mp-112 Firmware, Audiocodes Mp-114 Firmware, Audiocodes Mp-118 Firmware.

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

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

## Is CVE-2025-32106 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-32106 is a critical code injection vulnerability in n/a, published on 3 Jun 2025. 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-2025-32106 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-2025-32106/ (Markdown: https://insights.sbomify.com/CVE-2025-32106/index.md)
```

## Sources

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

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