# CVE-2026-23925: Zabbix incorrect authorization in configuration.import API

Source: https://junglewise.ai/threats/cve-2026-23925-zabbix-incorrect-authorization-in-configuration-import-api  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-03-06. Updated: 2026-06-05  
License: CC BY 4.0 with a link back

CVE-2026-23925 · Severity: high · CVSS 8.1 · Published 2026-03-06

Zabbix is an enterprise-grade monitoring solution used to track the health and performance of IT infrastructure. A security flaw allows low-privileged users to bypass standard restrictions and create unauthorized monitoring hosts or templates via the system's programming interface (API). This could allow an internal user to gain unauthorized access to infrastructure data or disrupt monitoring operations.

Technologies: [Zabbix](https://junglewise.ai/threats/technologies/zabbix). Vendors: [Zabbix](https://junglewise.ai/threats/vendors/zabbix).

## Quick answers

**Is CVE-2026-23925 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-23925 being exploited in the wild.

**How severe is CVE-2026-23925?** High severity, with a CVSS score of 8.1, published 6 March 2026.

**Which products and versions are affected?** Zabbix 6.0.0 - 6.0.40, 7.0.0 - 7.0.17, 7.4.0 - 7.4.1.

**Is there a fix for CVE-2026-23925?** A patch was published on 2026-03-18: Resolution confirmed fixed in tracking system Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-23925 attacked?** It is attacked over the network, in a network appliance.

**Am I affected by CVE-2026-23925?** Check whether you run Zabbix at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## Technical details

An incorrect authorization vulnerability (CWE-863) exists in the Zabbix configuration.import API. While the 'User' role is typically restricted from creating or editing templates and hosts even with write permissions, the API fails to properly enforce these role-based access controls during the import process. An authenticated attacker with low-level write permissions can leverage this to create unauthorized objects. The vulnerability affects Zabbix versions 6.0.x, 7.0.x, and 7.4.x. Patches are available in versions 6.0.41, 7.0.18, and 7.4.2.

## Affected products

- Zabbix Zabbix 6.0.0 - 6.0.40, 7.0.0 - 7.0.17, 7.4.0 - 7.4.1

## Timeline

- 2026-03-06: disclosed
- 2026-03-06: advisory
- 2026-03-18: patched: Resolution confirmed fixed in tracking system

## References

- [https://support.zabbix.com/browse/ZBX-27567](https://support.zabbix.com/browse/ZBX-27567)

## Related threats

- [Zabbix stored XSS in OAuth configuration form](https://junglewise.ai/threats/cve-2026-59788-the-email-media-type-oauth-form-passes-the-authorization-endpoint)
- [Zabbix Frontend credential disclosure via search filtering](https://junglewise.ai/threats/cve-2026-59785-host-search-in-frontend-allows-filtering-by-fields-that-are-not)
- [Zabbix API PSK key extraction in host.get](https://junglewise.ai/threats/cve-2026-23937-zabbix-api-psk-key-extraction-in-host-get)
- [Zabbix Frontend denial of service via validate.api.exists](https://junglewise.ai/threats/cve-2026-23934-zabbix-frontend-denial-of-service-via-validate-api-exists)
- [Zabbix Frontend session key disclosure in database](https://junglewise.ai/threats/cve-2026-23933-zabbix-frontend-session-key-disclosure-in-database)