CVE-2024-46613: WeeChat before 4.4.2 has an integer overflow and resultant buffer overflow at core/core-string.c when there ar
CVE-2024-46613 is a critical-severity flaw (CVSS 9.8) affecting weechat. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
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.
Why this priority
- Critical severity
- Remotely exploitable, no login, no user action
A fixed release or distro patch exists.
Risk facts
| CVSS score | 9.8 (Critical) |
| Attack vector | Network (remote) |
| Attack complexity | Low |
| Privileges needed | None |
| User interaction | None |
| EPSS exploit chance | 0.5% (top 59%) |
| CISA exploited list | No |
| Weakness | CWE-190 |
| Published | 2024-11-10 |
| Last modified | 2026-06-17 |
Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score
Am I affected?
Timeline
- Published CVE record published
- Updated Record last modified
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.
Quick answers
How do I fix CVE-2024-46613?
weechat: upgrade to 4.4.2. Exact commands for each OS are on this page.
Is CVE-2024-46613 being exploited?
CVE-2024-46613 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.
What does CVE-2024-46613 affect?
CVE-2024-46613 affects weechat. Severity is critical (CVSS 9.8). 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
How urgent is CVE-2024-46613?
Priority 50/100. Critical severity; Remotely exploitable, no login, no user action