# CVE-2025-63650: Denial of service in n/a

> Attackers can cause a Denial of Service in the Monkey web server by sending crafted HTTP requests that trigger an out-of-bounds read.

- **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:** No
- **Published:** 29 Jan 2026
- **Updated:** 3 Feb 2026
- **Also known as:** AZL-76355, AZL-76383, GHSA-pgh9-cmjh-p9cw

## What is CVE-2025-63650?

CVE-2025-63650 is a high-severity denial of service vulnerability in n/a, published on 29 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An out-of-bounds read in the mk_ptr_to_buf in mk_core function (mk_memory.c) of monkey commit f37e984 allows attackers to cause a Denial of Service (DoS) via sending a crafted HTTP request to the server.

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

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

It affects 1 product.


Products: Monkey-Project Monkey.

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

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

## Is CVE-2025-63650 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2013-2159](https://insights.sbomify.com/CVE-2013-2159/): Auth bypass in monkey (critical 9.8)
- [CVE-2025-63649](https://insights.sbomify.com/CVE-2025-63649/): Denial of service in n/a (high 7.5)
- [CVE-2025-63651](https://insights.sbomify.com/CVE-2025-63651/): Use after free in n/a (high 7.5)
- [CVE-2025-63652](https://insights.sbomify.com/CVE-2025-63652/): Use after free in n/a (high 7.5)
- [CVE-2025-63653](https://insights.sbomify.com/CVE-2025-63653/): Denial of service in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-63650 is a high-severity denial of service vulnerability in n/a, published on 29 Jan 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-2025-63650 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-63650/ (Markdown: https://insights.sbomify.com/CVE-2025-63650/index.md)
```

## Sources

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

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