cve.bz

CVE-2026-50144 tencent ncnn: Improper Validation of Array Index

7.1 highEPSS 0.2%

High (7.1) in tencent ncnn. EPSS 0.2% estimated probability of exploitation activity in the next 30 days.

On this page
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.

Severity

CVSS 3.1

7.1 high
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:H
EPSS
0.2% (unchanged from 0.2% a week ago; 0.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 5th percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: PoC · Automatable: no · Technical impact: total, assessed 2026-07-17. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-20 Improper Input Validation
CWE-129 Improper Validation of Array Index
CWE-787 Out-of-bounds Write
OWASP Top 10
A05:2025 Injection
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Ask an AI about this CVE

Show the promptExplain CVE-2026-50144 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-50144?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-50144?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-50144 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-50144

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-50144](https://cve.bz/cve/badge/CVE-2026-50144.svg)](https://cve.bz/cve/CVE-2026-50144)

HTML:

<a href="https://cve.bz/cve/CVE-2026-50144"><img src="https://cve.bz/cve/badge/CVE-2026-50144.svg" alt="CVE-2026-50144"></a>

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Tencent ncnn< 5a0288f255daa6c3294f77109f67718e434ec020
Tencent ncnn<= 20260526

Attack patterns (CAPEC)

  • CAPEC-100 Overflow Buffers Likelihood: High · Severity: Very High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-20 (51).

References

Check your stackJSON