dbcve.org
ZabbixApplication

CVE-2026-23925

HIGH · 8.1 CVSS v3.1 Published 2026-03-06
Fix available
A fix is available. Upgrade to 6.0.41 / 7.0.18 or later.
See remediation →
87/100
Remediation priority · High
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

An authenticated Zabbix user with User role and template/host write permissions can bypass normal authorization restrictions via the configuration.import API to create unauthorized hosts, leading to confidentiality loss. The User role is normally restricted from creating/editing hosts and templates, but the import function does not properly enforce these role-based restrictions.

MitigationRestrict or disable the configuration.import API capability for User role accounts and apply vendor-provided patches to properly enforce role-based access controls on import operations.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
ZabbixApplication
Affected:>= 6.0.0, < 6.0.41>= 7.0.0, < 7.0.18>= 7.4.0, < 7.4.2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Zabbix server version
    Access Zabbix web UI dashboard or run 'zabbix_server --version' on the server. The version is typically displayed in the UI footer or via the command line.
    Affected if The installed version falls within >= 6.0.0 and < 6.0.41, OR >= 7.0.0 and < 7.0.18, OR >= 7.4.0 and < 7.4.2
  2. Confirm User role is active with write permissions
    In Zabbix UI, navigate to Users > Users > select a user with User role. Go to Permissions tab and verify if the user has write permissions to Templates or Hosts groups.
    Affected if The user has the basic User role AND has been granted write permissions to templates or hosts
  3. Verify API access is enabled
    Check Administration > Scripts or verify API is not disabled in zabbix.conf. Confirm the configuration.import API endpoint is accessible (usually at /api_jsonrpc.php).
    Affected if API access is enabled and the configuration.import method is available to the user
  4. Review API audit logs for import operations
    Check Zabbix audit log (Reports > Audit) or system logs for recent configuration.import API calls performed by users with User role.
    Affected if Users with User role have successfully executed configuration.import to create hosts or templates despite lacking full permissions

A user is affected if running a Zabbix version within the affected ranges AND has users with User role granted write permissions to templates/hosts, allowing unauthorized object creation via the configuration.import API.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 6.0.41 / 7.0.18 / 7.4.2 or later
Fixed in 6.0.417.0.187.4.2
Interim mitigation

Restrict or disable the configuration.import API capability for User role accounts and apply vendor-provided patches to properly enforce role-based access controls on import operations.

Recommended fix High confidence

Upgrade to 6.0.41, 7.0.18, or 7.4.2 (or later) depending on your current major branch

  1. 1. Identify the current Zabbix version by checking Administration > System Information in the web UI or running `zabbix_server --version`
  2. 2. For Zabbix 6.0.x: Upgrade to version 6.0.41 or later
  3. 3. For Zabbix 7.0.x: Upgrade to version 7.0.18 or later
  4. 4. For Zabbix 7.4.x: Upgrade to version 7.4.2 or later
  5. 5. After upgrading, verify the fix by testing that users with only User role and write permissions cannot create hosts/templates via configuration.import API
  6. 6. Review user role permissions to ensure they align with least-privilege principles
Caveat Standard Zabbix upgrade considerations apply - review release notes for any breaking changes between versions, test in staging first

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Zabbix Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,980
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,168.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-23925 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-23925 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data