Skip to content
OpenAdvisories
High WID-SEC-2026-2916 11 CVEs

Zabbix: Mehrere Schwachstellen

Published Aug 18, 2026 · Updated Aug 18, 2026 · de-DE

Summary

Ein Angreifer kann mehrere Schwachstellen in Zabbix ausnutzen, um Informationen offenzulegen oder zu manipulieren, um Sicherheitsmechanismen zu umgehen, um einen Denial of Service herbeizuführen, um einen Cross-Site Scripting Angriff durchzuführen und potenziell um Code auszuführen.

Product

Zabbix ist ein Open-Source Netzwerk-Monitoringsystem.

Vulnerabilities 11

  • High 8.5

    Prototype pollution leading to stored XSS

    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 cha…

  • High 7.7

    Hardcoded session key in Zabbix 7.4

    In Zabbix 7.4 the cryptographic key used for signing Frontend sessions has been erroneously written to the database seed. Currently the only known exploitation scenario is for deployments that utilize both - SAML authentication and guest users. In such cases …

  • Medium 6.9

    API and Frontend login lockout race condition

    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.

  • Medium 6.8

    Use-after-free read in script item/preprocessing HttpRequest body

    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.

  • Medium 6.0

    Host PSK extraction in Zabbix API

    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.

  • Medium 5.4

    Improper validation of custom installation directories on Windows could allow installation into locations with unsafe permissions, increasing the risk of DLL sideloading.

    When Zabbix Agent was installed on Windows into a custom installation directory, the installer did not verify whether the selected directory had secure access permissions. If the target directory allowed unauthorized users to modify its contents, an attacker …

  • Medium 5.3

    Frontend DoS via the popup.testtriggerexpr action

    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.

  • Medium 5.3

    Frontend plaintext macro value enumeration via the validatate.api.exists action

    The frontend validatate.api.exists action can be exploited by authenticated users to extract plaintext user macro values leading to potential loss of confidentiality.

  • Medium 5.1

    Frontend DoS via the validate.api.exists action

    An authenticated user is able to cause disproportionate CPU load on the Frontend webserver by sending specifically crafted requests to the Frontend validate.api.exists action, leading to potential denial of service.

  • Low 2.1

    Email media OAuth secret leak to Super Admin

    The email media OAuth field 'Client secret' cannot be read after saving, but a Super Admin can leak it by setting a malicious 'Token endpoint'. Changes were made to reset the client secret upon changing the token endpoint.

  • Low 2.1

    Server DoS via JavaScript preprocessing or script items

    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.

Revision history

  1. #1

    Initiale Fassung

References