dbcve.org
Log ServerApplication · Nagios

CVE-2025-34274

CRITICAL · 9.8 CVSS v3.1 Published 2025-10-30
Fix available
A fix is available. Upgrade to 2024 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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 2024R2.0.3 contain an execution with unnecessary privileges vulnerability as it runs its embedded Logstash process as the root user. If an attacker is able to compromise the Logstash process - for example by exploiting an insecure plugin, pipeline configuration injection, or a vulnerability in input parsing - the attacker could execute code with root privileges, resulting in full system compromise. The Logstash service has been altered to run as the lower-privileged 'nagios' user to reduce this risk associated with a network-facing service that can accept untrusted input or load third-party components.

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 2024R2.0.3 run their embedded Logstash process as the root user, a high-privilege account. Because Logstash is a network-facing service that can accept untrusted input and load third-party plugins, an attacker who compromises Logstash through a plugin vulnerability, pipeline configuration injection, or input parsing flaw gains immediate root-level code execution, enabling full system compromise.

MitigationUpgrade Nagios Log Server to version 2024R2.0.3 or later, which configures Logstash to run as the unprivileged 'nagios' user instead of root.

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:< 2024= 2024

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

CVSS:3.1/AV:N/AC:L/PR:N/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
    Run 'rpm -q nagioslogserver' or check the Nagios Log Server web interface dashboard for the installed version number
    Affected if Version is 2024 or earlier (< 2024 or = 2024)
  2. Check if Logstash process runs as root
    Run 'ps aux | grep logstash' or 'ps -U root | grep logstash' to examine the user running the Logstash process
    Affected if Logstash process shows root as the effective user or owner
  3. Verify Logstash service configuration
    Check the Logstash service file (typically in /etc/systemd/system/ or examined via 'systemctl show logstash') for the User= and Group= directives
    Affected if Service is configured to run as User=root or Group=root
  4. Confirm Nagios Log Server is in use
    Verify the system has Nagios Log Server installed by checking for the /usr/local/nagioslogserver directory or by accessing the Nagios Log Server web interface
    Affected if Nagios Log Server software is present and running

If Nagios Log Server version is 2024 or earlier AND Logstash is confirmed to run as the root user, the environment is affected by this vulnerability.

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 2024 or later
Fixed in 2024
Interim mitigation

Upgrade Nagios Log Server to version 2024R2.0.3 or later, which configures Logstash to run as the unprivileged 'nagios' user instead of root.

Recommended fix High confidence

2024R2.0.3

  1. 1. Check the current Nagios Log Server version by navigating to the web interface or running the version command.
  2. 2. Backup all Nagios Log Server data and configuration files before proceeding with the upgrade.
  3. 3. Download Nagios Log Server version 2024R2.0.3 or later from the official Nagios website (www.nagios.com).
  4. 4. Run the upgrade installer following Nagios documentation for your specific installation method.
  5. 5. After upgrade, verify the Logstash service runs as the 'nagios' user instead of root by checking the service configuration.
  6. 6. Test that Log Server functionality remains operational after the upgrade.

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-34274 — 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-34274 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