dbcve.org
Log ServerApplication · Nagios

CVE-2025-34322

HIGH · 7.2 CVSS v3.1 Published 2025-11-17
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 Log Server versions prior to 2026R1.0.1 contain an authenticated command injection vulnerability in the experimental 'Natural Language Queries' feature. When this feature is configured, certain user-controlled settings—including model selection and connection parameters—are read from the global configuration and concatenated into a shell command that is executed via shell_exec() without proper input handling or command-line argument sanitation. An authenticated user with access to the 'Global Settings' page can supply crafted values in these fields to inject additional shell commands, resulting in arbitrary command execution as the 'www-data' user and compromise of the Log Server host.

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 Log Server versions prior to 2026R1.0.1 contain an authenticated command injection vulnerability in the experimental 'Natural Language Queries' feature. Authenticated users with access to Global Settings can supply crafted values in model selection and connection parameters that are directly concatenated into shell commands executed via shell_exec() without sanitization, resulting in arbitrary command execution as the www-data user.

MitigationUpgrade to Nagios Log Server 2026R1.0.1 or later to obtain the patched version. Until patched, limit access to the Global Settings page to only trusted administrators.

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
Log ServerApplication
Affected:< 2026= 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 Log Server version
    Locate the installed Nagios Log Server version through the web interface (typically in About or System Information page) or via command line tools used for Nagios installations
    Affected if The installed version is prior to 2026R1.0.1 or shows as version 2026 without the 2026R1.0.1 patch level
  2. Confirm Natural Language Queries feature is enabled
    Inspect the Global Settings configuration area for the Natural Language Queries or NLP Queries module and determine whether it is turned on or accessible
    Affected if The Natural Language Queries feature is enabled or available in the Global Settings interface
  3. Verify user access to Global Settings
    Check which user accounts or roles have permission to access the Global Settings page within the Nagios Log Server web interface
    Affected if Any user account other than fully trusted administrators has been granted access to Global Settings
  4. Inspect Natural Language Queries configuration parameters
    Examine the model selection and connection parameter fields within the Natural Language Queries feature for any unsanitized user-supplied values
    Affected if The feature allows direct input of model names or connection strings without evident input validation or escaping

A user is affected if they run Nagios Log Server prior to 2026R1.0.1, the Natural Language Queries feature is enabled, and untrusted users have access to Global Settings where malicious command payloads could be injected into model or connection parameters.

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 to Nagios Log Server 2026R1.0.1 or later to obtain the patched version. Until patched, limit access to the Global Settings page to only trusted administrators.

Recommended fix High confidence

2026R1.0.1

  1. 1. Identify current Nagios Log Server version by checking the admin interface or running: cat /usr/local/nagioslogserver/version.json
  2. 2. Create a complete backup of the Nagios Log Server configuration directory at /usr/local/nagioslogserver/nagioslogserver/settings/
  3. 3. Download Nagios Log Server version 2026R1.0.1 from the official Nagios downloads page at https://www.nagios.com/downloads/
  4. 4. Run the installer as root: sudo ./nagioslogserver-2026R1.0.1.x86_64.run
  5. 5. Follow the on-screen prompts to upgrade the existing installation
  6. 6. After upgrade, verify the version shows 2026R1.0.1 in the admin interface
  7. 7. Log out and log back in to ensure session tokens are refreshed
  8. 8. As an administrator, review the Natural Language Queries settings in Global Settings to confirm proper input validation is in place
Caveat Review release notes for any configuration schema changes or feature modifications between your current version and 2026R1.0.1

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

Fix this in Log Server Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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