Heap buffer over-read
The researcher is showing that it is possible to leak a small amount of Zabbix Server memory using an out of bounds read in src/libs/zbxmedia/email.c
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for the hundreds of thousands of vulnerabilities in the database; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for help- Published
- Nov 27, 2024
- Updated
- Jun 17, 2026
- EPSS
- 0.6% · 48th percentile
- CWE
- CWE-126
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
10
Monitor
Low priority for now.
- CVSS
- 10 / 40 · 2.7 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.6%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · Zabbix
- 2.7
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Affected systems
| Vendor | Product | CPE |
|---|---|---|
| zabbix | zabbix | cpe:2.3:a:zabbix:zabbix |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- zabbix zabbix6.0.0 and later · before 6.0.34
- zabbix zabbix6.4.0 and later · before 6.4.19
- zabbix zabbix7.0.0 and later · before 7.0.4
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Zabbix). Independent of NVD's CPE analysis and usually ahead of it.
Zabbix Zabbix
- 6.0.0 and later · up to and including 6.0.33affected · gitfixed in 6.0.34rc1
- 6.4.0 and later · up to and including 6.4.18affected · gitfixed in 6.4.19rc1
- 7.0.0 and later · up to and including 7.0.3affected · gitfixed in 7.0.4rc1
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:11 | zabbix | before 1:5.0.45+dfsg-1+deb11u1 | 1:5.0.45+dfsg-1+deb11u1 |
| Debian:12 | zabbix | all versions | — |
| Debian:13 | zabbix | before 1:7.0.5+dfsg-1 | 1:7.0.5+dfsg-1 |
| SUSE:Linux Enterprise Server LTSS Extended Security 12 SP5 | zabbix | before 4.0.12-4.32.1 | 4.0.12-4.32.1 |
Same product
zabbix: all recordsOther highest-scoring records for the same primary product.
- CVE-2022-23131Unsafe client-side session storage leading to authentication bypass/instance takeover via Zabbix Frontend with configured SAMLKEV98Now
- CVE-2022-23134Possible view of the setup pages by unauthenticated users if config file already existsKEV80Now
- CVE-2016-10134SQL injection vulnerability in Zabbix before 2.2.14 and 3.0 before 3.0.4 allows remote attackers to execute arbitrary SQL commands via the t64This week
- CVE-2024-42327SQL injection in user.get API63This week
- CVE-2013-5743Multiple SQL injection vulnerabilities in Zabbix 1.8.x before 1.8.18rc1, 2.0.x before 2.0.9rc1, and 2.1.x before 2.1.7.63This week
- CVE-2024-22120Time Based SQL Injection in Zabbix Server Audit Log58Plan
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Zabbix Zabbix | 6.0.34rc1 | Vendor (CNA) |
| Zabbix Zabbix | 6.4.19rc1 | Vendor (CNA) |
| Zabbix Zabbix | 7.0.4rc1 | Vendor (CNA) |
| debian:zabbix | 1:7.0.5+dfsg-1 · Debian:13 | Package registry (OSV) |
| suse:zabbix | 4.0.12-4.32.1 · SUSE:Linux Enterprise Server LTSS Extended Security 12 SP5 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
- chamalreporter
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- Administrator privileges are required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- low · data can be read
- Integrity
- none
- Availability
- none
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- Low
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
CWE-126 · Buffer Over-readCVSS vector
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:N/A:N
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.