---
id: CVE-2026-59781
title: >-
  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
summary: >-
  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 …
severity: high
cvss: 7.8
cvssVector: 'CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H'
cwe:
  - CWE-427
vendor: zabbix
product: zabbix
affected:
  - 'zabbix >= 6.0.0, < 6.0.48'
  - 'zabbix >= 7.0.0, < 7.0.29'
  - 'zabbix >= 7.4.0, < 7.4.13'
patched:
  - zabbix 7.4.13
published: '2026-08-18'
updated: '2026-09-23'
sourceUpdated: '2026-09-23T15:42:02.280'
source: NVD
sourceUrl: 'https://nvd.nist.gov/vuln/detail/CVE-2026-59781'
references:
  - url: 'https://support.zabbix.com/browse/ZBX-28077'
    label: security@zabbix.com
tags:
  - nvd
epss: 0.00117
epssPercentile: 0.01509
ingestedAt: '2026-09-23T16:27:22.631Z'
---

## Overview

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 could place a malicious DLL that could later be loaded by the application, resulting in DLL sideloading. The installer has been hardened to detect potentially unsafe installation directories and now requires explicit user confirmation before proceeding with installation in such locations. This reduces the risk of accidental installation into directories with inappropriate permissions while preserving compatibility with existing deployment scenarios.

## Affected

- `zabbix >= 6.0.0, < 6.0.48`
- `zabbix >= 7.0.0, < 7.0.29`
- `zabbix >= 7.4.0, < 7.4.13`

## Remediation

Upgrade past the affected range:

- `zabbix 7.4.13`