dbcve.org
ZabbixApplication

CVE-2025-27236

MEDIUM · 6.5 CVSS v3.1 Published 2025-10-03
Fix available
A fix is available. Upgrade to 6.0.41 / 7.0.17 or later.
See remediation →
71/100
Remediation priority · Elevated
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
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.

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

A regular Zabbix user can bypass intended access controls by using SELECT fields in API queries to retrieve user data from other users within their user group that they should not have permission to view. The API fails to properly validate field-level permissions when processing select parameters, allowing unauthorized data disclosure of sensitive user attributes.

MitigationApply vendor-supplied patches for CVE-2025-27236 and review API permission configurations to ensure field-level access controls are properly enforced.

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.38, < 6.0.41>= 7.0.9, < 7.0.17>= 7.2.3, < 7.2.11= 7.4.0

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
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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. Check Zabbix server version
    Run 'zabbix_server --version' or check the frontend via Administration > System information in the web UI, or query the API endpoint /api/version
    Affected if The installed version falls within >= 6.0.38 and < 6.0.41, >= 7.0.9 and < 7.0.17, >= 7.2.3 and < 7.2.11, or equals 7.4.0
  2. Verify API is accessible
    Confirm the Zabbix API endpoint is reachable (default: /api) and that regular (non-superadmin) user accounts exist in the system
    Affected if API is exposed and there are regular user accounts with limited permissions configured
  3. Review user role permissions for user.read
    Navigate to Administration > Users > Roles in the web UI and inspect the permissions assigned to user roles, specifically checking if the 'user.read' permission is granted with limited user group scoping
    Affected if Regular users have API access with user.read permission that is not properly restricted to their own user group only
  4. Check API audit logs for unauthorized user data access
    In the web UI, go to Reports > Audit logs and filter for API activity; look for user.get requests with select parameters that may indicate cross-user data retrieval
    Affected if Audit logs show API queries using select parameters that request fields from users outside the requester's authorized scope

A user is affected if they are running a Zabbix version in the affected ranges AND have the API enabled with regular user accounts that may be able to exploit the select parameter field-level permission bypass to view user data outside their authorized scope.

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.17 / 7.2.11 or later
Fixed in 6.0.417.0.177.2.11
Interim mitigation

Apply vendor-supplied patches for CVE-2025-27236 and review API permission configurations to ensure field-level access controls are properly enforced.

Recommended fix High confidence

Upgrade to Zabbix 6.0.41, 7.0.17, 7.2.11, or 7.4.1 (or later) depending on your current major version branch

  1. 1. Identify your current Zabbix version by checking the Zabbix web UI footer or running: zabbix_server -V
  2. 2. Based on your current version, determine the appropriate upgrade path to a fixed release
  3. 3. For Zabbix 6.0.x: upgrade to version 6.0.41 or later
  4. 4. For Zabbix 7.0.x: upgrade to version 7.0.17 or later
  5. 5. For Zabbix 7.2.x: upgrade to version 7.2.11 or later
  6. 6. For Zabbix 7.4.0: upgrade to version 7.4.1 or later
  7. 7. Review release notes and upgrade documentation at https://www.zabbix.com/documentation/ before upgrading
  8. 8. Perform a backup of your Zabbix database and configuration files
Caveat Standard Zabbix upgrade considerations apply; review release notes for any behavioral changes between versions

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

Fix this in Zabbix Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
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,328.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-27236 — 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-2025-27236 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