Breaking: Java4Shell (CVE-2026-114938) - Less Than 0.12% of JVMs Estimated at Risk of RCE
Read the Report
Learn How MCP Is Bypassing a Decade of Cloud Security Best Practices
Read the Report
Are you exposed? Connect a repo in minutes.
Scan your repos free

CVE-2024-46613

WeeChat before 4.4.2 has an integer overflow and resultant buffer over ...

Overview

Published
10 Nov 2024
Modified
17 Jun 2026
Critical CVE
0 Registry packages
9 OS packages
5 Linux distributions
Yes Fix available

Description

WeeChat before 4.4.2 has an integer overflow and resultant buffer overflow at core/core-string.c when there are more than two billion items in a list. This affects string_free_split_shared , string_free_split, string_free_split_command, and string_free_split_tags.

Source: OX vulnerability database

Severity

9.8 · CRITICAL

CVSS 3.1 base score, scored by NVD.

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Weakness: CWE-190

Affected packages · 0

No registry package. This ID affects operating system packages only.

Operating systems · 8 fixes

alpine 1 release · 1 package

fixed 1
weechat
alpine fixes for CVE-2024-46613
ReleasePackageFixed in
edge weechat 4.4.2-r0

debian 4 releases · 1 package

affected 2 fixed 2
weechat
debian fixes for CVE-2024-46613
ReleasePackageFixed in
11 weechat affected
12 weechat affected
13 weechat 4.4.2-1
14 weechat 4.4.2-1

echo 1 release · 1 package

fixed 1
weechat
echo fixes for CVE-2024-46613
ReleasePackageFixed in
weechat 4.4.2-1

openSUSE 1 release · 1 package

fixed 1
weechat
openSUSE fixes for CVE-2024-46613
ReleasePackageFixed inAdvisory
Tumbleweed weechat +8 4.5.1-1.1 openSUSE-SU-2025:14734-1

ubuntu 1 release · 1 package

affected 1
weechat
ubuntu fixes for CVE-2024-46613
ReleasePackageFixed in
18.04-ESM weechat affected

References

OX Radar and Response Center

Find threats in your stack.

OX Radar can check high-priority threats, like critical package CVEs, against your context.

Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.