# CVE-2026-112073: Tencent ncnn MatMul matmul.cpp matmul_transb out-of-bounds

> An out-of-bounds read in Tencent ncnn's MatMul layer allows remote attackers to cause denial of service or read sensitive memory.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 19 Oct 2026
- **Updated:** 22 Oct 2026
- **Also known as:** GHSA-fx59-v8wm-992x

## What is CVE-2026-112073?

CVE-2026-112073 is a medium-severity memory corruption vulnerability in Tencent ncnn, published on 19 Oct 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

A vulnerability was identified in Tencent ncnn up to 44b02dabdcf97499281a4692ebd65bad73dcf8b6. Affected by this vulnerability is the function matmul_transb of the file src/layer/matmul.cpp of the component MatMul. The manipulation leads to out-of-bounds read. The attack can be initiated remotely. The exploit is publicly available and might be used. The project was informed of the problem early through an issue report but has not responded yet.

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-2026-112073?


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

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

## Is CVE-2026-112073 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-112073 is a medium-severity memory corruption vulnerability in Tencent ncnn, published on 19 Oct 2026. An attacker can exploit it over the internet without logging in, 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-112073 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-112073/ (Markdown: https://insights.sbomify.com/CVE-2026-112073/index.md)
```

## Sources

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

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