Signal is active with 2 mentions in latest observed window
Recommended action window: Monitor and triage in normal cycle
NVD description
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
Priority
LOW
Exploitation
NONE
PoC
NONE
Patch
NONE
Momentum
NONE
CVE-2026-18370 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-l… https://www.cve.org/CVERecord?id=CVE-2026-18370
Post summary
The post announces CVE-2026-18370, detailing a heap-based buffer overflow in entr's run_utility() caused by a fixed-size buffer allocation and includes a link to the CVE record.
🚨*CVE* CVE-2026-18370 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-l… https://www.cve.org/CVERecord?id=CVE-2026-18370 ----- Traducción: CVE-2026-18370 ent… http://infoflow.cloud`
Post summary
The post announces CVE‑2026‑18370, a heap buffer overflow in entr’s run_utility() routine, but offers no PoC, exploit, or patch information.