Quick answers
- Is CVE-2026-59139 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-59139 being exploited in the wild.
- How severe is CVE-2026-59139?
- Informational severity, published 21 July 2026.
- Which products and versions are affected?
- EGOR Data ReqRep::Shared before 0.05.
- Is there a fix for CVE-2026-59139?
- A patch was published on 2026-07-21: Fixed in version 0.05 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-59139 attacked?
- It is attacked with local access, in a software library.
- Am I affected by CVE-2026-59139?
- Check whether you run EGOR Data ReqRep::Shared at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
An out-of-bounds read vulnerability exists in Data::ReqRep::Shared before version 0.05 due to insufficient validation of memory offsets. The function reqrep_recv_locked performs a memcpy using an offset and length read directly from a memory-mapped (mmap'd) segment without verifying them against the actual arena capacity (req_arena_cap). A local attacker who can modify the backing file can poison these values while maintaining a valid header. When the process attempts to receive the request, it may read adjacent memory or crash. This issue is addressed in version 0.05.
Affected products
- EGOR Data::ReqRep::Shared before 0.05
Timeline
- 2026-07-21: advisory
- 2026-07-21: disclosed
- 2026-07-21: patched: Fixed in version 0.05