Debian Package Tracker
Register | Log in
Subscribe

zabbix

Choose email to subscribe with

general
  • source: zabbix (main)
  • version: 1:7.0.29+dfsg-2
  • maintainer: Dmitry Smirnov (DMD)
  • uploaders: Christoph Haas [DMD]
  • arch: all any
  • std-ver: 4.6.2
  • VCS: Git (Browse, QA)
versions [more versions can be listed by madison] [old versions available from snapshot.debian.org]
[pool directory]
  • o-o-stable: 1:5.0.8+dfsg-1
  • o-o-sec: 1:5.0.47+dfsg-0+deb11u1
  • oldstable: 1:6.0.14+dfsg-1
  • old-bpo: 1:7.0.9+dfsg-1~bpo12+1
  • stable: 1:7.0.22+dfsg-1~deb13u1
  • stable-bpo: 1:7.0.22+dfsg-1~bpo13+1
  • testing: 1:7.0.29+dfsg-2
  • unstable: 1:7.0.29+dfsg-2
versioned links
  • 1:5.0.8+dfsg-1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
  • 1:5.0.47+dfsg-0+deb11u1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
  • 1:6.0.14+dfsg-1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
  • 1:7.0.9+dfsg-1~bpo12+1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
  • 1:7.0.22+dfsg-1~bpo13+1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
  • 1:7.0.22+dfsg-1~deb13u1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
  • 1:7.0.29+dfsg-2: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
binaries
  • zabbix-agent (3 bugs: 0, 2, 1, 0)
  • zabbix-agent2 (1 bugs: 0, 1, 0, 0)
  • zabbix-frontend-php (3 bugs: 0, 1, 2, 0)
  • zabbix-java-gateway
  • zabbix-proxy-mysql (1 bugs: 0, 0, 1, 0)
  • zabbix-proxy-pgsql
  • zabbix-proxy-sqlite3
  • zabbix-sender
  • zabbix-server-mysql (4 bugs: 0, 1, 3, 0)
  • zabbix-server-pgsql (1 bugs: 0, 1, 0, 0)
  • zabbix-web-service
action needed
Marked for autoremoval on 13 October due to golang-github-go-logr-logr: #1146195 high
Version 1:7.0.29+dfsg-2 of zabbix is marked for autoremoval from testing on Tue 13 Oct 2026. It depends (transitively) on golang-github-go-logr-logr, affected by #1146195. You should try to prevent the removal by fixing these RC bugs.
Created: 2026-09-06 Last update: 2026-09-08 10:32
A new upstream version is available: 7.0.30 high
A new upstream version 7.0.30 is available, you should consider packaging it.
Created: 2026-08-27 Last update: 2026-09-08 10:01
18 security issues in bullseye high

There are 18 open security issues in bullseye.

13 important issues:
  • CVE-2026-1199: Zabbix API and Frontend login lockout mechanism has a flaw where several unsuccessful login requests are not properly counted towards the block counter if sent simultaneously, potentially allowing for more password guesses than intended.
  • CVE-2026-23919: For performance reasons Zabbix Server/Proxy reuses JavaScript (Duktape) contexts (used in script items, JavaScript reprocessing, Webhooks). This can lead to confidentiality loss where a regular (non-super) Zabbix administrator leaks data for hosts they do not have access to. A fix has been released that makes the built in Zabbix JavaScript objects read-only, but please be advised that usage of global JavaScript variables is not recommended because their content could be leaked. More information <a href='https://www.zabbix.com/documentation/7.4/en/manual/installation/known_issues#preprocessing-global-variables-are-unsafe'>in Zabbix documentation</a>.
  • CVE-2026-23920: Host and event action script input is validated with a regex (set by the administrator), but the validation runs in multiline mode. If ^ and $ anchors are used in user input validation, an injected newline lets authenticated users bypass the check and inject shell commands.
  • CVE-2026-23921: A low privilege Zabbix user with API access can exploit a blind SQL injection vulnerability in include/classes/api/CApiService.php to execute arbitrary SQL selects via the sortfield parameter. Although query results are not returned directly, an attacker can exfiltrate arbitrary database data through time-based techniques, potentially leading to session identifier disclosure and administrator account compromise.
  • CVE-2026-23924: Zabbix Agent 2 Docker plugin does not properly sanitize the 'docker.container_info' parameters when forwarding them to the Docker daemon. An attacker capable of invoking Agent 2 can read arbitrary files from running Docker containers by injecting them via the Docker archive API.
  • CVE-2026-23926: An authenticated (non-super) administrator can create a maintenance period with a JavaScript payload that is executed by any user that opens tooltip for that maintenance period in the Host navigator widget. This can allow the attacker to perform unauthorized actions depending on which user opens the tooltip.
  • CVE-2026-23927: A user able to connect to Agent 2 can inject an Oracle TNS connection string via the 'service' parameter. This can lead to Agent 2 connecting to an attacker-controlled server and leaking Oracle database credentials if they are saved in a named session.
  • CVE-2026-23928: The Item history widget (in Zabbix 7.0+) or the Plain text widget (in Zabbix 6.0) can execute injected JavaScript when HTML display is enabled. This can allow an attacker to perform unauthorized actions depending on which user opens a dashboard containing these widgets. The malicious JavaScript would have to come from a monitored host controlled by the attacker. Note: the Item history widget is a replacement for the Plain text widget since Zabbix 7.0.
  • CVE-2026-23929: Prototype pollution vulnerability in searchParamsToObject() is leading to a persistent XSS in Maps. URL parameter processing was not filtering dangerous properties like __proto__, combined with jQuery's unsafe element creation that traversed the prototype chain.
  • CVE-2026-23930: An unauthenticated user is able to cause disproportionate CPU load on the Frontend webserver by sending specifically crafted requests to the Frontend popup.testtriggerexpr action, leading to potential denial of service.
  • CVE-2026-23935: A Zabbix administrator is able to read out of bounds memory by utilizing a flaw in script item/preprocessing (JavaScript) HttpRequest logic, leading to potential confidentiality loss.
  • CVE-2026-23937: The Zabbix API host.get action can be exploited by authenticated users to extract a host's PSK key leading to potential loss of data integrity.
  • CVE-2026-23938: An authenticated administrator is able to crash Zabbix server or proxy by creating specifically crafted preprocessing/script item JavaScript scripts, leading to potential denial of service.
1 issue postponed or untriaged:
  • CVE-2026-23925: (postponed; to be fixed through a stable update) An authenticated Zabbix user (User role) with template/host write permissions is able to create objects via the configuration.import API. This can lead to confidentiality loss by creating unauthorized hosts. Note that the User role is normally not sufficient to create and edit templates/hosts even with write permissions.
4 ignored issues:
  • CVE-2025-27231: The LDAP 'Bind password' value cannot be read after saving, but a Super Admin account can leak it by changing LDAP 'Host' to a rogue LDAP server. To mitigate this, the 'Bind password' value is now reset on 'Host' change.
  • CVE-2025-27236: A regular Zabbix user can search other users in their user group via Zabbix API by select fields the user does not have access to view. This allows data-mining some field values the user does not have access to.
  • CVE-2025-49641: A regular Zabbix user with no permission to the Monitoring -> Problems view is still able to call the problem.view.refresh action and therefore still retrieve a list of active problems.
  • CVE-2025-49643: An authenticated Zabbix user (including Guest) is able to cause disproportionate CPU load on the webserver by sending specially crafted parameters to /imgstore.php, leading to potential denial of service.
Created: 2026-03-27 Last update: 2026-08-28 04:50
1 bug tagged patch in the BTS normal
The BTS contains patches fixing 1 bug, consider including or untagging them.
Created: 2026-09-02 Last update: 2026-09-08 11:30
Depends on packages which need a new maintainer normal
The packages that zabbix depends on which need a new maintainer are:
  • dh-linktree (#980413)
    • Build-Depends: dh-linktree
Created: 2019-11-22 Last update: 2026-09-08 11:00
Does not build reproducibly during testing normal
A package building reproducibly enables third parties to verify that the source matches the distributed binaries. It has been identified that this source package produced different results, failed to build or had other issues in a test environment. Please read about how to improve the situation!
Created: 2026-08-28 Last update: 2026-09-08 10:33
lintian reports 22 warnings normal
Lintian reports 22 warnings about this package. You should make the package lintian clean getting rid of them.
Created: 2026-08-23 Last update: 2026-08-23 16:49
10 low-priority security issues in trixie low

There are 10 open security issues in trixie.

3 issues left for the package maintainer to handle:
  • CVE-2026-23924: (needs triaging) Zabbix Agent 2 Docker plugin does not properly sanitize the 'docker.container_info' parameters when forwarding them to the Docker daemon. An attacker capable of invoking Agent 2 can read arbitrary files from running Docker containers by injecting them via the Docker archive API.
  • CVE-2026-23927: (needs triaging) A user able to connect to Agent 2 can inject an Oracle TNS connection string via the 'service' parameter. This can lead to Agent 2 connecting to an attacker-controlled server and leaking Oracle database credentials if they are saved in a named session.
  • CVE-2026-23937: (needs triaging) The Zabbix API host.get action can be exploited by authenticated users to extract a host's PSK key leading to potential loss of data integrity.

You can find information about how to handle these issues in the security team's documentation.

7 ignored issues:
  • CVE-2026-1199: Zabbix API and Frontend login lockout mechanism has a flaw where several unsuccessful login requests are not properly counted towards the block counter if sent simultaneously, potentially allowing for more password guesses than intended.
  • CVE-2026-23926: An authenticated (non-super) administrator can create a maintenance period with a JavaScript payload that is executed by any user that opens tooltip for that maintenance period in the Host navigator widget. This can allow the attacker to perform unauthorized actions depending on which user opens the tooltip.
  • CVE-2026-23928: The Item history widget (in Zabbix 7.0+) or the Plain text widget (in Zabbix 6.0) can execute injected JavaScript when HTML display is enabled. This can allow an attacker to perform unauthorized actions depending on which user opens a dashboard containing these widgets. The malicious JavaScript would have to come from a monitored host controlled by the attacker. Note: the Item history widget is a replacement for the Plain text widget since Zabbix 7.0.
  • CVE-2026-23929: Prototype pollution vulnerability in searchParamsToObject() is leading to a persistent XSS in Maps. URL parameter processing was not filtering dangerous properties like __proto__, combined with jQuery's unsafe element creation that traversed the prototype chain.
  • CVE-2026-23930: An unauthenticated user is able to cause disproportionate CPU load on the Frontend webserver by sending specifically crafted requests to the Frontend popup.testtriggerexpr action, leading to potential denial of service.
  • CVE-2026-23935: A Zabbix administrator is able to read out of bounds memory by utilizing a flaw in script item/preprocessing (JavaScript) HttpRequest logic, leading to potential confidentiality loss.
  • CVE-2026-23938: An authenticated administrator is able to crash Zabbix server or proxy by creating specifically crafted preprocessing/script item JavaScript scripts, leading to potential denial of service.
Created: 2026-03-27 Last update: 2026-09-05 11:30
debian/patches: 3 patches to forward upstream low

Among the 15 debian patches available in version 1:7.0.29+dfsg-2 of the package, we noticed the following issues:

  • 3 patches where the metadata indicates that the patch has not yet been forwarded upstream. You should either forward the patch upstream or update the metadata to document its real status.
Created: 2024-09-05 Last update: 2026-08-23 16:51
Standards version of the package is outdated. wishlist
The package should be updated to follow the last version of Debian Policy (Standards-Version 4.7.4 instead of 4.6.2).
Created: 2024-04-07 Last update: 2026-08-23 12:20
testing migrations
  • This package will soon be part of the auto-openssl transition. You might want to ensure that your package is ready for it. You can probably find supplementary information in the debian-release archives or in the corresponding release.debian.org bug.
news
[rss feed]
  • [2026-08-28] zabbix 1:7.0.29+dfsg-2 MIGRATED to testing (Debian testing watch)
  • [2026-08-23] Accepted zabbix 1:7.0.29+dfsg-2 (source) into unstable (Dmitry Smirnov)
  • [2026-08-23] Accepted zabbix 1:7.0.29+dfsg-1 (source) into unstable (Dmitry Smirnov)
  • [2026-08-20] Accepted zabbix 1:7.0.27+dfsg-1 (source) into unstable (Dmitry Smirnov)
  • [2026-07-05] zabbix REMOVED from testing (Debian testing watch)
  • [2026-05-11] zabbix 1:7.0.22+dfsg-1.1 MIGRATED to testing (Debian testing watch)
  • [2026-05-06] Accepted zabbix 1:7.0.22+dfsg-1.1 (source) into unstable (Adrian Bunk)
  • [2026-03-05] Accepted zabbix 1:7.0.22+dfsg-1~deb13u1 (source) into proposed-updates (Debian FTP Masters) (signed by: Bastien ROUCARIÈS)
  • [2026-02-08] Accepted zabbix 1:5.0.47+dfsg-0+deb11u1 (source) into oldoldstable-security (Bastien Roucariès) (signed by: Bastien ROUCARIÈS)
  • [2026-01-29] Accepted zabbix 1:7.0.22+dfsg-1~bpo13+1 (source amd64 all) into stable-backports (Debian FTP Masters) (signed by: Dmitry Smirnov)
  • [2026-01-29] zabbix 1:7.0.22+dfsg-1 MIGRATED to testing (Debian testing watch)
  • [2026-01-24] Accepted zabbix 1:7.0.22+dfsg-1 (source) into unstable (Dmitry Smirnov)
  • [2025-11-06] zabbix REMOVED from testing (Debian testing watch)
  • [2025-04-19] Accepted zabbix 1:5.0.46+dfsg-1+deb11u1 (source) into oldstable-security (Tobias Frost)
  • [2025-03-17] zabbix 1:7.0.10+dfsg-2 MIGRATED to testing (Debian testing watch)
  • [2025-03-12] Accepted zabbix 1:7.0.10+dfsg-2 (source) into unstable (Dmitry Smirnov)
  • [2025-02-28] Accepted zabbix 1:7.0.10+dfsg-1 (source) into unstable (Dmitry Smirnov)
  • [2025-02-28] Accepted zabbix 1:7.0.9+dfsg-1~bpo12+1 (source) into stable-backports (Dmitry Smirnov)
  • [2025-02-04] zabbix 1:7.0.9+dfsg-1 MIGRATED to testing (Debian testing watch)
  • [2025-01-29] Accepted zabbix 1:7.0.9+dfsg-1 (source) into unstable (Dmitry Smirnov)
  • [2025-01-01] zabbix REMOVED from testing (Debian testing watch)
  • [2024-12-07] Accepted zabbix 1:5.0.45+dfsg-1+deb11u1 (source) into oldstable-security (Tobias Frost)
  • [2024-11-29] zabbix 1:7.0.6+dfsg-1 MIGRATED to testing (Debian testing watch)
  • [2024-11-24] Accepted zabbix 1:7.0.6+dfsg-1 (source) into unstable (Dmitry Smirnov)
  • [2024-11-06] Accepted zabbix 1:7.0.5+dfsg-1~bpo12+1 (source) into stable-backports (Dmitry Smirnov)
  • [2024-11-06] zabbix 1:7.0.5+dfsg-1 MIGRATED to testing (Debian testing watch)
  • [2024-11-01] Accepted zabbix 1:7.0.5+dfsg-1 (source) into unstable (Dmitry Smirnov)
  • [2024-10-03] Accepted zabbix 1:5.0.44+dfsg-1+deb11u1 (source) into oldstable-security (Tobias Frost)
  • [2024-09-10] zabbix 1:7.0.3+dfsg-1 MIGRATED to testing (Debian testing watch)
  • [2024-09-05] Accepted zabbix 1:7.0.3+dfsg-1 (source) into unstable (Dmitry Smirnov)
  • 1
  • 2
bugs [bug history graph]
  • all: 19
  • RC: 0
  • I&N: 9
  • M&W: 10
  • F&P: 0
  • patch: 1
links
  • homepage
  • lintian (0, 22)
  • buildd: logs, reproducibility, cross
  • popcon
  • browse source code
  • other distros
  • security tracker
  • l10n (-, 53)
  • debian patches
ubuntu Ubuntu logo [Information about Ubuntu for Debian Developers]
  • version: 1:7.0.27+dfsg-1
  • 74 bugs (1 patch)

Debian Package Tracker — Copyright 2013-2025 The Distro Tracker Developers
Report problems to the tracker.debian.org pseudo-package in the Debian BTS.
Documentation — Bugs — Git Repository — Contributing