dbcve.org
Nagios XiApplication · Nagios

CVE-2025-34286

HIGH · 7.2 CVSS v3.1 Published 2025-10-30
Fix available
A fix is available. Upgrade to 2026 or later.
See remediation →
78/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
Nagios XI versions prior to 2026R1 contain a remote code execution vulnerability in the Core Config Manager (CCM) Run Check command. Insufficient validation/escaping of parameters used to build backend command lines allows an authenticated administrator to inject shell metacharacters that are executed on the server. Successful exploitation results in arbitrary command execution with the privileges of the Nagios XI web application user and can be leveraged to gain control of the underlying host operating system.

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

Nagios XI versions prior to 2026R1 contain an authenticated remote code execution vulnerability in the Core Config Manager (CCM) Run Check command. Insufficient validation and escaping of parameters when building backend command lines allows an authenticated administrator to inject shell metacharacters that are executed on the server with the privileges of the Nagios XI web application user.

MitigationUpgrade Nagios XI to version 2026R1 or later to obtain the patched code with proper input validation and escaping in the CCM Run Check functionality.

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
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/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. Identify Nagios XI installation and version
    Check the Nagios XI version by accessing the web interface (usually at /nagiosxi or /xi), or run: cat /usr/local/nagiosxi/etc/version.ini on the server
    Affected if Version shown is earlier than 2026R1 (or the version file shows a number less than 2026)
  2. Verify CCM component is enabled
    Log into the Nagios XI web interface and navigate to the Core Config Manager (CCM) section, typically found under 'Configure' > 'Core Config Manager' in the left-hand menu
    Affected if CCM interface is accessible and loads without errors
  3. Confirm administrator authentication to CCM
    Check user permissions in Nagios XI by going to 'Admin' > 'System Information' > 'Users' or by attempting to access CCM run check functionality - an admin user is required for this vulnerability
    Affected if Logged-in user has administrator privileges in Nagios XI CCM
  4. Locate the Run Check command feature
    In CCM, navigate to the 'Run Check' option - this is typically under monitoring configurations where checks can be manually executed, such as 'Configure' > 'Run Check' or within specific host/service configuration pages
    Affected if Run Check command interface is present and accessible to the authenticated administrator
  5. Inspect server user context
    Run 'ps aux | grep nagios' or check which user owns the Nagios XI web processes to determine the privileges under which the CCM Run Check commands would execute
    Affected if Commands would run as the Nagios XI web application user (typically 'nagios' or 'apache' or 'www-data') rather than a privileged root user

Your environment is affected if Nagios XI is installed with a version prior to 2026R1, you have administrator access to the CCM, and the Run Check feature is enabled and accessible in 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.

dbcve · scoped
Upgrade available Upgrade to 2026 or later
Fixed in 2026
Interim mitigation

Upgrade Nagios XI to version 2026R1 or later to obtain the patched code with proper input validation and escaping in the CCM Run Check functionality.

Recommended fix High confidence

2026R1

  1. 1. Back up the current Nagios XI installation, including the /usr/local/nagios directory and the MySQL/MariaDB database
  2. 2. Download Nagios XI version 2026R1 from the official Nagios website (www.nagios.com)
  3. 3. Run the Nagios XI upgrade installer as root: ./upgrade-xigraph
  4. 4. Follow the on-screen prompts to complete the upgrade process
  5. 5. After upgrade, clear browser cache and log into the Nagios XI web interface
  6. 6. Navigate to the Core Config Manager (CCM) and verify the Run Check command functionality works correctly
  7. 7. Confirm the version number shows 2026R1 in the Nagios XI admin page

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

Fix this in Nagios Xi Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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