CVE-2026-72852
HIGHDescription
hank-ai/darknet sizes a convolutional layer's weight and output heap buffers by multiplying configuration fields taken from a .cfg file in unchecked 32-bit int arithmetic. In src-lib/convolutional_layer.cpp, l.nweights is computed as (c / groups) * n * size * size and l.outputs as l.out_h * l.out_w * l.out_c, and both feed xcalloc directly. A .cfg whose true dimension product exceeds INT_MAX wraps to a small or zero value, so the allocation is undersized; for example width and height of 256 with filters of 65536 gives 2^32, which wraps to 0. forward_convolutional_layer then re-derives the GEMM dimensions with a different operand order, computing k as l.size*l.size*l.c / l.groups where the allocation divided before multiplying, and reads and writes through the undersized buffer. Loading the crafted .cfg for inference or training is sufficient and no valid .weights file is required. The reported proof of concept observed a heap buffer overflow read in gemm_nn_fast under AddressSanitizer and glibc allocator metadata corruption in a release build of the same input, indicating an out-of-bounds write.
How to fix
No published remediation has been found for this vulnerability's affected products yet.
Mitigation guidance may be in the linked vendor advisories in the References section below.
TridentStack Control tracks known vulnerabilities across your Windows, macOS, and Linux fleet and shows the fix as soon as one is published. See how it works
CVSS v3 Vector
Exploitability
Impact
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Exploit Intelligence
Low risk: more likely to be exploited than 4% of all known CVEs.
References
Related Vulnerabilities
Other CWE-190 (Integer Overflow) vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2020-16040 | Medium | 6.5 | 100% | - | Fix |
| CVE-2019-11477 | High | 7.5 | 99% | - | Fix |
| CVE-2023-44443 | High | 7.8 | 94% | - | Fix |
| CVE-2014-0569 | High | 9.3 | 92% | - | - |
| CVE-2017-3599 | High | 7.5 | 84% | - | Fix |
| CVE-2023-21716 | Critical | 9.8 | 82% | - | Fix |
Common questions
How do I fix CVE-2026-72852?
No published fix for CVE-2026-72852 has been found yet. Check the linked vendor advisories for guidance as it becomes available.
Is CVE-2026-72852 being actively exploited?
Not that we know of. CVE-2026-72852 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.14% is the estimated probability that it will be exploited in the next 30 days. That is higher than 4% of all scored CVEs.
How severe is CVE-2026-72852?
CVE-2026-72852 has a CVSS v3 base score of 7.8, rated high. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
Embed a live status badge for CVE-2026-72852
Markdown
[](https://tridentstack.com/cve/CVE-2026-72852)HTML
<a href="https://tridentstack.com/cve/CVE-2026-72852"><img src="https://tridentstack.com/cve/badge/CVE-2026-72852.svg" alt="CVE-2026-72852"></a>Find and fix vulnerabilities across your fleet
TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-08-25.