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.
CVE-2026-50144
This high-severity CVE scores 7.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.1%, top 99% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.1
- EG Score
- 7.1(medium)
- EG Risk
- 48(Track*)EG Risk 48/100SSVC: Track*
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity71% × 45%Exploitation40% × 40%Automatability0% × 15%Action: Watch closely — could escalate to Attend. - EPSS
- 1.4%
- KEV
- Not listed
Published
July 15, 2026
Last Modified
July 17, 2026
Advisory Details (2)
Auto-updated Jul 15, 2026Out-of-bounds heap write in ParamDict::load_param via unchecked negative parameter id · Advisory · Tencent/ncnn · GitHub
https://github.com/Tencent/ncnn/security/advisories/GHSA-jxmc-3mv6-7pwrcommit 5a0288f255da (Tencent/ncnn)
Fix landed in Tencent/ncnn commit 5a0288f255da — awaiting tagged release
https://github.com/Tencent/ncnn/commit/5a0288f255daa6c3294f77109f67718e434ec020Weakness Classification(3)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 7× in last 7d / 11× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-24 14:18 UTCEPSS rescore
- 2026-07-23 14:18 UTCEPSS rescore
- 2026-07-23 03:18 UTCEG score recompute
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-20 17:08 UTCEPSS rescore
- 2026-07-19 14:31 UTCEPSS rescore
- 2026-07-19 14:31 UTCEPSS rescore
- 2026-07-17 13:37 UTCEG score recompute
- 2026-07-16 17:03 UTCEPSS rescore
- 2026-07-15 20:10 UTCEG score recompute
- 2026-07-15 20:09 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-50144?
When was CVE-2026-50144 disclosed?
Is CVE-2026-50144 actively exploited?
What is the CVSS score of CVE-2026-50144?
How do I remediate CVE-2026-50144?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-50144
Is Your Infrastructure Affected by CVE-2026-50144?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.