Skip to main content
VulnerabilityPublished Updated

CVE-2022-48620: uev · Classic Buffer Overflow

Source CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical : upgrade to 2.4.1 as a priority.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
1.3% chance of exploitation in 30 days – higher than 70% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2.4.1
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 12 Jan 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade troglobit/libuev to 2.4.1.

Affected software

ProductAffectedFixed in
GitHubtroglobit/libuevpkg:github/troglobit/libuevOther threatsAffected
  • <2.4.1
Fixed in
  • 2.4.1

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

European organizations should take immediate steps to mitigate this vulnerability beyond generic advice: 1) Inventory and identify all systems and devices using libuev, especially embedded and IoT devices, to assess exposure. 2) Prioritize upgrading libuev to version 2.4.1 or later where possible, as this version addresses the buffer overflow issue. 3) For devices or applications where upgrading is not immediately feasible, implement network-level controls such as firewall rules to restrict access to services that may invoke epoll_wait with untrusted input. 4) Employ runtime application self-protection (RASP) or memory protection mechanisms (e.g., ASLR, DEP) to reduce exploitation success. 5) Monitor network traffic and system logs for anomalous behavior indicative of exploitation attempts, such as unusual epoll_wait calls or crashes. 6) Engage with vendors and suppliers to obtain patches or mitigation guidance for embedded devices incorporating libuev. 7) Incorporate this vulnerability into vulnerability management and incident response plans to ensure rapid detection and remediation.

Description

uev (aka libuev) before 2.4.1 has a buffer overflow in epoll_wait if maxevents is a large number.

References

Community reviews

Loading reviews…