CVE-2026-18370: Heap-based buffer overflow in entr

Published Aug 10, 2026
·
Updated

entr is vulnerable to Heap-based buffer overflow in runutility() function. The function allocates a fixed-size heap buffer using malloc(ARGMAX) 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 sizet, 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

Affected Software

1 affected component
entr

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade entr to a version that resolves this vulnerability.

    Patch 2467fe0

Event History

Aug 10, 2026
CVE Published
via MITRE·12:56 PM
Data Sourced
via MITRE·12:56 PM
DescriptionWeakness
Data Sourced
via NVD·01:17 PM
DescriptionSeverityWeakness
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-18370?

CVE-2026-18370 has a risk score of 37, indicating a medium level of severity.

2

How does CVE-2026-18370 affect entr?

CVE-2026-18370 affects the entr application by introducing a heap-based buffer overflow vulnerability in the run_utility() function.

3

What causes the vulnerability in CVE-2026-18370?

CVE-2026-18370 is caused by the use of malloc(ARG_MAX) to allocate a fixed-size heap buffer that is vulnerable to overflow when copying command-line arguments.

4

How can I mitigate CVE-2026-18370?

To mitigate CVE-2026-18370, ensure that you update entr to the latest version that patches this vulnerability.

5

Are there any known exploits for CVE-2026-18370?

As of now, there are no publicly disclosed exploits specifically targeting CVE-2026-18370.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203