OS Command InjectionWeakness · CWE-78

CVE-2025-27234

HIGH · 7.3 CVSS v4.0 Published 2025-09-12

Mitigation only

No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.

See remediation →

75/100

Remediation priority · High

Zero-click

Official description

NVD · unedited

Zabbix Agent 2 smartctl plugin does not properly sanitize smart.disk.get parameters, allowing an attacker to inject unexpected arguments into the smartctl command. In Zabbix 5.0 this allows for remote code execution.

Technical summary

dbcve analysis · high confidence

Zabbix Agent 2 smartctl plugin fails to sanitize smart.disk.get parameters, enabling injection of arbitrary arguments into the smartctl command. This command injection flaw allows remote code execution in Zabbix 5.0 environments.

MitigationUpdate Zabbix to a patched version that properly sanitizes smartctl plugin parameters. If immediate patching is not possible, restrict network access to the Zabbix Agent and disable the smartctl plugin.

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

CVSS breakdown

From the vector

Attack vector: Adjacent
Complexity: Low
Privileges: High
Authentication: X
User interaction: None
Scope: X

CVSS:4.0/AV:A/AC:L/AT:P/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Am I affected?

dbcve checks

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

Identify Zabbix Agent 2 installation

Run 'zabbix_agent2 --version' or check for /usr/sbin/zabbix_agent2 binary, or look for zabbix-agent2 package via package manager (dpkg -l | grep zabbix or rpm -qa | grep zabbix)

Affected if Zabbix Agent 2 is installed
Verify smartctl plugin is present

Check for the smartctl plugin file in the Zabbix Agent 2 plugins directory (typically /usr/lib/zabbix/plugins/ or /usr/lib64/zabbix/plugins/), or run 'zabbix_agent2 -p' to list available items and look for 'smart.disk.get'

Affected if The smartctl plugin is loaded and smart.disk.get item is available
Determine Zabbix Agent 2 version

Run 'zabbix_agent2 --version' and capture the version number; compare against Zabbix 5.0.x branch (e.g., 5.0.0 through 5.0.x where the vulnerability exists)

Affected if Version is within Zabbix 5.0.x branch
Check for active smart.disk.get monitoring items

Review Zabbix agent configuration files (zabbix_agent2.conf.d/) for 'smart.disk.get' items, or query the Zabbix server API/frontend for active items of type 'smart.disk.get'

Affected if Any smart.disk.get item is configured and active

A user is affected if Zabbix Agent 2 version 5.0.x is running with the smartctl plugin enabled and the smart.disk.get item is configured for monitoring

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

Remediation

dbcve · scoped

Mitigation available No clean upgrade yet — mitigate in the meantime

Mitigation

Update Zabbix to a patched version that properly sanitizes smartctl plugin parameters. If immediate patching is not possible, restrict network access to the Zabbix Agent and disable the smartctl plugin.

Recommended fix Moderate confidence

Zabbix 5.0.40+ or latest stable 6.0/7.0 LTS release

1. Identify the currently installed Zabbix Agent 2 version using: zabbix_agent2 --version
2. If running Zabbix 5.0.x, upgrade to the latest patched release in the 5.0 LTS series (e.g., 5.0.40 or later)
3. If running an older version, upgrade to the latest stable Zabbix release (6.0.x LTS or 7.0.x) which contains the fix
4. After upgrading, restart the Zabbix Agent 2 service: systemctl restart zabbix-agent2
5. Verify the smartctl plugin works correctly with: zabbix_agent2 -t smart.disk.get["<disk_device>"]
6. Review Zabbix server configuration to ensure only authorized hosts can request agent items

Caveat Minor - smart.disk.get parameter validation may reject previously accepted malformed input; test in staging before production deployment

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

Have this fixed Scoped from the published advisory

Consultation3.0 h
Implementation6.0 h
Testing3.0 h
Review / QA2.0 h

14.0 hours of engineering $2,490

Get help mitigating

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

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

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

Primary sources

Practitioner notes

Contributed

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

Notes0 Guidelines

Know something about CVE-2025-27234?

The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.

The version that genuinely resolved it — not the one the vendor claimed
A config change or rule that shut the vector down
A gotcha in the upgrade path that cost you an afternoon

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

At a glance

A fix existsA vendor remedy is published

Severity 7.3 High

Exploit likelihood EPSS, next 30 days 0.3%

Remediation

A high-priority fix

Have this fixed 14 hrs · Moderate

Typical engagement from $2,490

Get a fix See the full breakdown ↓

A high-priority vulnerability. Send your environment and a specialist will scope CVE-2025-27234 and return a fixed quote and timeline.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

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.

Check your environment

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.

Scan for this in your stack

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

Practitioner notes

No notes yet

Official description

Technical summary

CVSS breakdown

Am I affected?

Remediation

References