eradman entr up to 5.8 run_utility heap-based overflow

Summaryinfo

A vulnerability, which was classified as problematic, has been found in eradman entr up to 5.8. The impacted element is the function run_utility. This manipulation causes heap-based overflow. This vulnerability appears as CVE-2026-18370. The attack requires local access. There is no available exploit.

Detailsinfo

A vulnerability was found in eradman entr up to 5.8. It has been declared as problematic. Affected by this vulnerability is the function run_utility. The manipulation with an unknown input leads to a heap-based overflow vulnerability. The CWE definition for the vulnerability is CWE-122. A heap overflow condition is a buffer overflow, where the buffer that can be overwritten is allocated in the heap portion of memory, generally meaning that the buffer was allocated using a routine such as malloc(). As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:

entr is vulnerable to Heap-based buffer overflow in run_utility() function. The function allocates a fixed-size heap buffer using malloc(ARG_MAX) and copies command-line arguments into it. It advances the destination pointer based on the return value of strlcpy(), which returns the total length of the source string rather than the number of bytes written. When the buffer is exactly filled, the remaining size underflows as an unsigned size_t, causing subsequent copies to write out of bounds. This can be triggered by supplying command-line arguments whose combined length fills the buffer, or via the /_ substitution feature which expands a short token into a longer pathname at runtime. The local attacker can cause memory corruption, process abort, and denial of service.  This issue was fixed in commit 2467fe0

The advisory is shared at cert.pl. This vulnerability is known as CVE-2026-18370 since 07/30/2026. The exploitation appears to be easy. An attack has to be approached locally. Technical details are known, but no exploit is available.

Applying the patch 2467fe0 is able to eliminate this problem.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Vendor

• eradman

Name

• entr

Version

• 5.0
• 5.1
• 5.2
• 5.3
• 5.4
• 5.5
• 5.6
• 5.7
• 5.8

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion