CVE-2024-36466 | Unauthenticated Zabbix frontend takeover when SSO is being used

A bug in the code allows an attacker to sign a forged zbx_session cookie, which then allows them to sign in with admin permissions.

Published: 2024-11-28 Last update: 2025-10-08 Assigner: [email protected] Source: [email protected]
NVD Status：Analyzed，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2024-36466 is rated Moderate Risk (52.4/100): CVSS High severity, with low exploitation likelihood (EPSS 0.25%). Review affected assets and schedule remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

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

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-04-19 0.19% 0.25% +0.07%
2 2026-03-08 0.14% 0.19% +0.04%
3 2026-02-17 — 0.14% —

Full EPSS history (10 records total)

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

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
8.8 3.1 HIGH
CVSS:3.1/AV:N/AC:L/PR:L/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:L)
A normal user session is enough; they don’t have to be admin.
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.
 2.8 5.9 [email protected]

Weakness enumeration for CVE-2024-36466

OS Trackers for CVE-2024-36466

vendor priority summary link
alpine — CVE-2024-36466: 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-36466
debian unimportant CVE-2024-36466 unimportant priority: Debian including 1 source packages (zabbix), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 4, open 1. https://security-tracker.debian.org/tracker/CVE-2024-36466
suse high CVE-2024-36466 severity important: 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-36466/
ubuntu medium CVE-2024-36466 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 5, not-affected 3, DNE 1, released 1. https://ubuntu.com/security/CVE-2024-36466

Affected software / configurations for CVE-2024-36466

Vendor Product Version Raw CPE
zabbix zabbix >= 6.0.0, < 6.0.32 cpe:2.3:a:zabbix:zabbix:*:*:*:*:*:*:*:*
zabbix zabbix >= 6.4.0, < 6.4.17 cpe:2.3:a:zabbix:zabbix:*:*:*:*:*:*:*:*
zabbix zabbix 7.0.0 cpe:2.3:a:zabbix:zabbix:7.0.0:-:*:*:*:*:*:*

References for CVE-2024-36466

cvelogic Threat Intelligence