dbcve.org
Nagios XiApplication · Nagios

CVE-2026-2041

HIGH · 8.8 CVSS v3.1 Published 2026-02-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
High EPSS 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
Nagios Host zabbixagent_configwizard_func Command Injection Remote Code Execution Vulnerability. This vulnerability allows remote attackers to execute arbitrary code on affected installations of Nagios Host. Authentication is required to exploit this vulnerability. The specific flaw exists within the zabbixagent_configwizard_func method. The issue results from the lack of proper validation of a user-supplied string before using it to execute a system call. An attacker can leverage this vulnerability to execute code in the context of the service account. Was ZDI-CAN-28250.

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

This is an authenticated command injection vulnerability in Nagios Host's zabbixagent_configwizard_func method. The flaw exists due to improper validation of user-supplied input before it's used in a system call, allowing authenticated attackers to execute arbitrary code in the context of the service account.

MitigationValidate and sanitize all user-supplied input in zabbixagent_configwizard_func before using it in system calls, preferably by avoiding system calls altogether and using parameterized methods or safe API alternatives.

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
Nagios XiApplication
Affected:= 2026

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
High

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

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. Confirm Nagios XI installation and version
    Locate the Nagios XI installation and identify the installed version. Common paths include /usr/local/nagiosxi/ or /opt/nagiosxi/. Check version file: cat /usr/local/nagiosxi/etc/version.ini or similar version file in the installation directory.
    Affected if Installed version is exactly 2026 (matches the affected version range)
  2. Verify zabbixagent_configwizard_func is accessible
    Check if the Zabbix agent configuration wizard is enabled in the Nagios XI web interface. This typically involves checking the Nagios XI configuration for Zabbix agent monitoring capabilities, often found under the 'Configure' or ' Wizards' section of the web interface.
    Affected if Zabbix agent configuration wizard feature is enabled and accessible in the web interface
  3. Confirm web interface authentication status
    Verify that the Nagios XI web interface is configured with authentication enabled. Check configuration files (typically in /usr/local/nagiosxi/etc/ or similar) for authentication settings, and confirm that user login is required to access configuration features.
    Affected if Web interface authentication is disabled or allows unauthenticated access to the configuration wizards (note: CVE states authenticated attacker required, so if authentication is disabled, the attack surface is wider)
  4. Identify if Zabbix monitoring is configured
    Check Nagios XI configuration for any Zabbix-related host configurations or monitoring profiles. Look for configuration files or the database that contain zabbix_agent or zabbix-related host definitions.
    Affected if Zabbix agent monitoring is actively configured or the wizard has been accessed previously

Environment is affected only if Nagios XI version is exactly 2026 AND the Zabbix agent configuration wizard (zabbixagent_configwizard_func) is accessible and enabled, AND an attacker can authenticate to the web interface.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Validate and sanitize all user-supplied input in zabbixagent_configwizard_func before using it in system calls, preferably by avoiding system calls altogether and using parameterized methods or safe API alternatives.

Fix this in Nagios Xi Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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