CVE-2024-36468 [Low] | Memory Corruption in Zabbix

The reported vulnerability is a stack buffer overflow in the zbx_snmp_cache_handle_engineid function within the Zabbix server/proxy code. This issue occurs when copying data from session->securityEngineID to local_record.engineid without proper bounds checking.

#	Date	Old EPSS score	New EPSS score	Delta (New - Old)
1	2026-04-18	0.36%	0.49%	+0.13%
2	2026-01-13	0.21%	0.36%	+0.16%
3	2026-01-05	—	0.21%	—

Date

Old EPSS score

New EPSS score

Delta (New - Old)

2026-04-18

0.36%

0.49%

+0.13%

2026-01-13

0.21%

0.36%

+0.16%

2026-01-05

—

0.21%

—

Base score	Version	Severity	Vector	Exploitability	Impact	Score source
3.0	3.1	LOW	`CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:L/I:N/A:N` 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:H) Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work. Privileges required (PR:H) They need powerful rights—admin, root, or similar—before this pays off. User interaction (UI:N) Nobody has to click “OK” or open a trap file; it can work without a victim helping. Scope (S:C) Breaking this can reach past the original component and bite other resources—bigger blast radius. Confidentiality (C:L) Some sensitive info could get out, but not a total data dump. Integrity (I:N) Data isn’t meaningfully altered or forged. Availability (A:N) Service keeps running; no real outage angle.	1.3	1.4	[email protected]
8.2	3.1	HIGH	`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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:L) Some sensitive info could get out, but not a total data dump. Integrity (I:N) Data isn’t meaningfully altered or forged. Availability (A:H) Could take the service down hard or make it unusable for people who depend on it.	3.9	4.2	[email protected]

Base score

Version

Severity

Vector

Exploitability

Impact

Score source

3.0

3.1

LOW

CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:L/I:N/A:N 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:H): Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work.
Privileges required (PR:H): They need powerful rights—admin, root, or similar—before this pays off.
User interaction (UI:N): Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:C): Breaking this can reach past the original component and bite other resources—bigger blast radius.
Confidentiality (C:L): Some sensitive info could get out, but not a total data dump.
Integrity (I:N): Data isn’t meaningfully altered or forged.
Availability (A:N): Service keeps running; no real outage angle.

1.3

1.4

[email protected]

8.2

3.1

HIGH

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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:L): Some sensitive info could get out, but not a total data dump.
Integrity (I:N): Data isn’t meaningfully altered or forged.
Availability (A:H): Could take the service down hard or make it unusable for people who depend on it.

3.9

4.2

[email protected]

OS Trackers for CVE-2024-36468

vendor	priority	summary	link
`alpine`	—	CVE-2024-36468: 1 source package rows (zabbix); 2 state rows across 2 repos (3.22-community, edge-community); fixed 0, open 2.	https://security.alpinelinux.org/vuln/CVE-2024-36468
`debian`	unimportant	CVE-2024-36468 unimportant priority: Debian including 1 source packages (zabbix), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5.	https://security-tracker.debian.org/tracker/CVE-2024-36468
`suse`	medium	CVE-2024-36468 severity moderate: SUSE including 2 source package names (zabbix, zabbix-agent), 7 product×package rows across 5 product lines (SUSE Linux Enterprise Server 12 SP4-LTSS, SUSE Linux Enterprise Server 12 SP5-LTSS, … (5 product lines)): Known Not Affected 7.	https://www.suse.com/security/cve/CVE-2024-36468/
`ubuntu`	medium	CVE-2024-36468 medium priority: Ubuntu including 1 source packages (zabbix), 10 status rows across 10 suites (bionic, focal, jammy, noble, oracular, plucky, questing, trusty, upstream, xenial): needs-triage 7, ignored 2, DNE 1.	https://ubuntu.com/security/CVE-2024-36468

Affected software / configurations for CVE-2024-36468

Vendor	Product	Version	Raw CPE
zabbix	zabbix	>= 7.0.0, < 7.0.3	cpe:2.3:a:zabbix:zabbix::::::::

References for CVE-2024-36468

URL	Tags
https://support.zabbix.com/browse/ZBX-25621	Vendor Advisory

URL

CVE-2024-36468 | Stack buffer overflow in zbx_snmp_cache_handle_engineid

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

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

Weakness enumeration for CVE-2024-36468

OS Trackers for CVE-2024-36468

Affected software / configurations for CVE-2024-36468

References for CVE-2024-36468