CVE-2026-81334

MediumCVSS 6.1

Published: 27/08/2026(UTC)Updated: 27/08/2026(UTC)Translated: 31/08/2026(UTC)NVD NIST

Exploitation Probability (EPSS)

Low risk

0.13%

3th percentile - higher than 3% of all known CVEs

Summary

Darknet has a vulnerability where the layer array is indexed with a value from a configuration file without bounds checking, leading to out-of-bounds read and write. Parsing a crafted configuration file is sufficient to cause a crash and a controlled write.

Risk Assessment

An attacker can cause a reliable crash and a write past the allocation, potentially leading to unpredictable behavior or code execution depending on the file's content.

Recommendation

Update Darknet to a patched version that adds bounds checking. If not possible, avoid processing untrusted configuration files.

Other vulnerabilities in Darknet

CVE-2026-72852High
hank-ai/darknet has a vulnerability where convolutional layer weight and output heap buffers are sized using unchecked 32-bit integer arithmetic on configuration fields from a .cfg file. A crafted .cfg can cause undersized allocation, leading to heap buffer overflow during forward_convolutional_layer. Loading the crafted .cfg is sufficient, no valid .weights file is required.

Original NVD description (English source)

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.