# CVE-2026-50144: ncnn: Out-of-bounds heap write in ParamDict::load_param via unchecked negative parameter id

> Attackers can trigger out-of-bounds heap writes in ncnn by providing a malicious model file with negative parameter IDs, potentially leading to code execution or crashes.

- **Severity:** High 7.1 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 15 Jul 2026
- **Updated:** 17 Jul 2026
- **Also known as:** GHSA-jxmc-3mv6-7pwr

## What is CVE-2026-50144?

CVE-2026-50144 is a high-severity memory corruption vulnerability in Tencent ncnn, published on 15 Jul 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

ncnn is a high-performance neural network inference framework optimized for the mobile platform. In commit e54f7b1f88434e1d844ea0551b880a1cfb079ce1 and earlier, ncnn allows an out-of-bounds heap write in ncnn::ParamDict::load_param() when Net::load_param() loads a malicious .param model file because the parsed parameter id is checked only against id >= NCNN_MAX_PARAM_COUNT, allowing a negative id to index before the params[NCNN_MAX_PARAM_COUNT] array. This vulnerability is fixed by commit 5a0288f255daa6c3294f77109f67718e434ec020.

Weakness: CWE-787 (Out-of-bounds Write), CWE-20 (Improper Input Validation), CWE-129 (Improper Validation of Array Index)

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


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

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

## Is CVE-2026-50144 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-50144 is a high-severity memory corruption vulnerability in Tencent ncnn, published on 15 Jul 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-50144 exists.

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

## Sources

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

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