CVE-2026-81334
MEDIUMDescription
darknet subscripts its layer array with an index taken from a configuration file without checking it against the array's length. The array is allocated in src-lib/darknet_network.cpp as xcalloc(net.n, sizeof(Darknet::Layer)), sized to exactly the number of layer sections the file declares. The shortcut, scale_channels and sam sections supply that index through their from field and the route section through its layers field, and parse_shortcut_section in src-lib/darknet_cfg.cpp reads net.layers[index].outputs with no bounds check, which reads past the allocation. The dispatch loop in create_network then reuses the same index to assign net.layers[l.index].use_bin_output and net.layers[l.index].keep_delta_gpu, writing past the allocation at an offset the file controls, with a fixed one-byte value. Parsing a crafted configuration file is sufficient: the parse runs before any weights file is opened and needs no non-default option, so the result is a reliable crash and a write whose location, though not its value, is chosen by whoever supplied the file.
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:N/I:L/A:H
Exploit Intelligence
Low risk: more likely to be exploited than 3% of all known CVEs.
References
Related Vulnerabilities
Other CWE-125 (Out-of-bounds Read) vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2014-0160 | High | 7.5 | 100% | KEV | Fix |
| CVE-2025-5777 | High | 7.5 | 100% | KEV + Ransom | Fix |
| CVE-2021-4034 | High | 7.8 | 95% | KEV + Ransom | Fix |
| CVE-2020-8794 | Critical | 9.8 | 89% | - | Fix |
| CVE-2023-49285 | High | 8.6 | 89% | - | Fix |
| CVE-2023-21769 | High | 7.5 | 89% | - | Fix |
Common questions
How do I fix CVE-2026-81334?
No published fix for CVE-2026-81334 has been found yet. Check the linked vendor advisories for guidance as it becomes available.
Is CVE-2026-81334 being actively exploited?
Not that we know of. CVE-2026-81334 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.13% is the estimated probability that it will be exploited in the next 30 days. That is higher than 3% of all scored CVEs.
How severe is CVE-2026-81334?
CVE-2026-81334 has a CVSS v3 base score of 6.1, rated medium. 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-81334
Markdown
[](https://tridentstack.com/cve/CVE-2026-81334)HTML
<a href="https://tridentstack.com/cve/CVE-2026-81334"><img src="https://tridentstack.com/cve/badge/CVE-2026-81334.svg" alt="CVE-2026-81334"></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-27.