CVE-2024-46613 [Critical] | Integer Overflow in Weechat

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.

#	Date	Old EPSS score	New EPSS score	Delta (New - Old)
1	2026-04-01	0.29%	0.47%	+0.18%
2	2025-12-19	0.38%	0.29%	-0.09%
3	2025-11-21	—	0.38%	—

Date

Old EPSS score

New EPSS score

Delta (New - Old)

2026-04-01

0.29%

0.47%

+0.18%

2025-12-19

0.38%

0.29%

-0.09%

2025-11-21

—

0.38%

—

Base score	Version	Severity	Vector	Exploitability	Impact	Score source
9.8	3.1	CRITICAL	`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H` Click to expand Attack vector (AV:N) Could be attacked over the internet or any normal routed network—not just someone sitting at the machine. Attack complexity (AC:L) Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup. Privileges required (PR:N) No account or special rights needed—anonymous or random user is enough. User interaction (UI:N) Nobody has to click “OK” or open a trap file; it can work without a victim helping. Scope (S:U) Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems. Confidentiality (C:H) Serious risk that confidential data gets exposed in a big way. Integrity (I:H) They could widely tamper with or forge data—trust in the data is badly hurt. Availability (A:H) Could take the service down hard or make it unusable for people who depend on it.	3.9	5.9	[email protected]
4.3	3.1	MEDIUM	`CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L` Click to expand Attack vector (AV:P) Hands-on access—USB, keyboard, opening the case—not something you do purely over the wire. Attack complexity (AC:L) Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup. Privileges required (PR:N) No account or special rights needed—anonymous or random user is enough. User interaction (UI:N) Nobody has to click “OK” or open a trap file; it can work without a victim helping. Scope (S:U) Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems. Confidentiality (C:L) Some sensitive info could get out, but not a total data dump. Integrity (I:L) Attackers could change some data, but it’s limited—not everything goes. Availability (A:L) Might cause slowdowns, glitches, or partial disruption—not a full brick.	0.9	3.4	134c704f-9b21-4f2e-91b3-4a467353bcc0

Base score

Version

Severity

Vector

Exploitability

Impact

Score source

9.8

3.1

CRITICAL

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

Attack vector (AV:N): Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L): Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N): No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N): Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U): Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H): Serious risk that confidential data gets exposed in a big way.
Integrity (I:H): They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H): Could take the service down hard or make it unusable for people who depend on it.

3.9

5.9

[email protected]

4.3

3.1

MEDIUM

CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L Click to expand

Attack vector (AV:P): Hands-on access—USB, keyboard, opening the case—not something you do purely over the wire.
Attack complexity (AC:L): Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N): No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N): Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U): Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:L): Some sensitive info could get out, but not a total data dump.
Integrity (I:L): Attackers could change some data, but it’s limited—not everything goes.
Availability (A:L): Might cause slowdowns, glitches, or partial disruption—not a full brick.

0.9

3.4

134c704f-9b21-4f2e-91b3-4a467353bcc0

OS Trackers for CVE-2024-46613

vendor	priority	summary	link
`alpine`	medium	CVE-2024-46613: 1 source package rows (weechat); 7 state rows across 3 repos (3.20-community, 3.22-community, edge-community); fixed 0, open 7.	https://security.alpinelinux.org/vuln/CVE-2024-46613
`debian`	not yet assigned	CVE-2024-46613 not yet assigned priority: Debian including 1 source packages (weechat), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 3, open 2.	https://security-tracker.debian.org/tracker/CVE-2024-46613
`ubuntu`	medium	CVE-2024-46613 medium priority: Ubuntu including 1 source packages (weechat), 9 status rows across 9 suites (bionic, focal, jammy, noble, oracular, plucky, questing, upstream, xenial): needs-triage 5, not-affected 2, ignored 1, released 1.	https://ubuntu.com/security/CVE-2024-46613

Affected software / configurations for CVE-2024-46613

Vendor	Product	Version	Raw CPE
weechat	weechat	>= 0.1.6, < 4.4.2	cpe:2.3:a:weechat:weechat::::::::

References for CVE-2024-46613

URL	Tags
https://github.com/weechat/weechat/issues/2178	Issue Tracking Third Party Advisory
https://weechat.org/doc/weechat/security/WSA-2024-1/	Vendor Advisory

URL

CVE-2024-46613

Exploit prediction scoring system (EPSS) score for CVE-2024-46613

Common vulnerability scoring system (CVSS) metrics for CVE-2024-46613

Weakness enumeration for CVE-2024-46613

OS Trackers for CVE-2024-46613

Affected software / configurations for CVE-2024-46613

References for CVE-2024-46613