Skip to main content

Nagios Log Server CVE-2025-34277

CRITICAL
Code Injection (CWE-94)
2025-10-30 disclosure@vulncheck.com
9.4
CVSS 4.0 · Vendor: vulncheck
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Authenticate with low-privilege Log Server account
  2. Delivery
    Submit malformed dashboard ID to endpoint
  3. Exploit
    Unvalidated value forwarded to internal API
  4. Execution
    Attacker data executed (CWE-94)
  5. Impact
    Arbitrary code execution as Log Server process

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Code injection prevention, sandbox exec
MITRE ATT&CK

2 techniques across 2 tactics: Execution, Initial Access

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Exploitation requires an authenticated session on Nagios Log Server with at least low-level privileges (CVSS PR:L) - it is NOT exploitable by unauthenticated attackers - and the ability to reach the dashboard functionality that accepts a dashboard ID value which is forwarded to the internal API. The specific prerequisite is the capacity to supply a crafted/malformed dashboard ID through that dashboard workflow; no special non-default product configuration, platform, or user interaction is stated as required (AT:N/UI:N). The primary limiting factor is therefore the authentication requirement; realistic risk is highest in deployments where low-privilege accounts are broadly provisioned or where the application is network-exposed to semi-trusted users.

Impact

This is a credible priority rather than a high-CVSS-but-low-risk issue, though the risk is gated by one key factor. The CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:L/UI:N) describes network-reachable, low-complexity exploitation requiring no user interaction, and CWE-94 code injection yielding arbitrary code execution in the Log Server process context - a severe technical impact (VC:H/VI:H/VA:H). The single most important mitigating signal is PR:L: an attacker needs at least low-privilege authenticated access to the Log Server application, so this is NOT an unauthenticated internet-facing RCE. No EPSS score, KEV listing, or POC indicator was provided in the input, so there is no public exploit identified at time of analysis and no evidence of active exploitation; the one differentiating intelligence signal is that the flaw was reported by VulnCheck, a credible vulnerability-research vendor, which raises the likelihood that exploitation detail is understood even if not public. Conflicting/missing data: the provided CVSS 4.0 asserts subsequent-system impact (SC:H/SI:H/SA:H) but the description only establishes code execution within the Log Server process itself - the subsequent-system scope is not substantiated by the description and should be verified with the vendor. No SSVC decision data was supplied.

Exploit ScenarioDerived

An attacker with a valid low-privilege account on Nagios Log Server submits a crafted, malformed dashboard ID value which is passed unvalidated to an internal API, causing attacker-controlled data to be executed and yielding arbitrary code execution as the Log Server process. Given AV:N/AC:L, this is a single low-complexity network request once authenticated. No public proof-of-concept was identified in the provided data, though the issue is documented in a VulnCheck advisory.

Act Now Prioritize within 24-48h. Why: CRITICAL severity.
No patch listed yet 2.2% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 07, 2026

Remote code execution in Nagios Log Server versions prior to 2024R1.3.1 allows an authenticated low-privileged attacker to execute arbitrary code in the context of the Log Server process by supplying a malformed dashboard ID to an internal API. The vulnerability is rated CVSS 9.4 (CVSS 4.0) but requires authentication (PR:L), and no public exploit code has been identified at time of analysis. This is a credible priority rather than a high-CVSS-but-low-risk issue, though the risk is gated by the authentication requirement.

RemediationAI

Vendor-released patch: upgrade to Nagios Log Server 2024R1.3.1 or later. Apply the update from the official changelog at https://www.nagios.com/changelog/#log-server-2024R1 and consult the security page at https://www.nagios.com/products/security/#log-server. If immediate patching is not possible, restrict access to the dashboard functionality and the Nagios Log Server web interface to trusted networks and users, enforce strong authentication, and monitor logs for unusual dashboard ID parameters. Note that these compensating controls reduce the attack surface but do not eliminate the vulnerability, and they may limit legitimate dashboard usage. Additional technical details are available at https://www.vulncheck.com/advisories/nagios-log-server-rce-via-malformed-dashboard-id.

Affects your stack

Find out whether the stacks and servers you run are on an affected version.

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The vulnerability is a code injection (CWE-94) in Nagios Log Server's dashboard functionality. A dashboard ID parameter is not properly validated before being forwarded to an internal API, allowing an attacker to inject and execute arbitrary code. The affected component is the internal API that processes dashboard IDs, which likely performs dynamic evaluation or command construction without sanitization. According to CPE data, all versions of Nagios Log Server prior to 2024R1.3.1 are affected, including specific 2024 releases R1, R1.0.1, R1.0.2, R1.1, R1.2, and R1.3. The root cause is the lack of input neutralization for special elements that are later interpreted as code, enabling an authenticated attacker with low privileges (CVSS 4.0 PR:L) to achieve code execution. No special non-default configuration, platform, or user interaction is required (AT:N/UI:N), but an authenticated session with at least low-level privileges is a prerequisite.

Know when Nagios gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (vulncheck) PRIMARY 9.4 CRITICAL
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H
vuln.today AI 8.8 HIGH

Network-reachable low-complexity injection needing a low-privilege account (PR:L); full compromise of the Log Server process gives C/I/A:H with scope unchanged as impact stays within that process.

3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
4.0 AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (vulncheck).

CVSS VectorVendor: vulncheck

Attack Vector
Network
Attack Complexity
Low
Attack Requirements
None
Privileges Required
Low
User Interaction
None
Vulnerable system: Confidentiality
High
Vulnerable system: Integrity
High
Vulnerable system: Availability
High
Subsequent system: Confidentiality
High
Subsequent system: Integrity
High
Subsequent system: Availability
High

DescriptionCVE.org

Nagios Log Server versions prior to 2024R1.3.1 contain a code injection vulnerability where malformed dashboard ID values are not properly validated before being forwarded to an internal API. An attacker able to supply crafted dashboard ID values can cause the system to execute attacker-controlled data, leading to arbitrary code execution in the context of the Log Server process.

Executive ViewAI

Why It Matters

A critical remote code execution vulnerability in Nagios Log Server, affecting all releases prior to 2024R1.3.1, allows anyone holding a valid low-privilege account to run arbitrary code as the Log Server service through a malformed dashboard ID passed to an internal API. The affected platform is typically the centralized repository for authentication and security telemetry, so a compromise could let an intruder read sensitive log data, disable monitoring, and use the server as a foothold for lateral movement. Leadership should care because the only barrier to exploitation is a single valid user account, and no vendor patch is confirmed as available at time of analysis.

Business Impact: High
Compensating Controls

No vendor-released patch is confirmed at time of analysis. Interim mitigations: restrict network reachability of the Nagios Log Server web UI and internal API to trusted management networks or a VPN with strict ACLs; enforce least privilege by removing unnecessary and stale accounts and reviewing all accounts with API access; enable multi-factor authentication for all interactive logins; place the application behind a reverse proxy or WAF with rules that reject malformed dashboard ID parameters and unexpected API request patterns; segment the Log Server host from other production systems; centrally collect and alert on its own logs for suspicious API calls; and rotate administrative and service credentials on a defined schedule until the upgrade to 2024R1.3.1 is complete.

Threat Intelligence Overview

EPSS Score
2.2%
Top 18% exploitable
Prevalence
Low
niche commercial log-management product; smaller footprint than Nagios Core monitoring
Data Quality
2 sources
Confidence: Low

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity CRITICAL
CISA KEV No
Public POC No
EPSS 2.2%
Patch available No
Active threat No
Deciding rule
CRITICAL severity
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation· derived
None
System Exposure· derived
Open
Automatable· derived
No
Human Impact
High

Priority Score

49
Low Medium High Critical
KEV: 0
EPSS: +2
CVSS: +47
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Code Injection CRITICAL

Code injection occurs when an application accepts user input and passes it directly into a language interpreter or evaluator without proper sanitization.

Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.

Affected Products (CPE)CVE.org

cpe:2.3:a:nagios:log_server:*:*:*:*:*:*:*:*
cpe:2.3:a:nagios:log_server:2024:r1:*:*:*:*:*:*
cpe:2.3:a:nagios:log_server:2024:r1.0.1:*:*:*:*:*:*
cpe:2.3:a:nagios:log_server:2024:r1.0.2:*:*:*:*:*:*
cpe:2.3:a:nagios:log_server:2024:r1.1:*:*:*:*:*:*
cpe:2.3:a:nagios:log_server:2024:r1.2:*:*:*:*:*:*
cpe:2.3:a:nagios:log_server:2024:r1.3:*:*:*:*:*:*

More in Nagios

View all
CVE-2021-25298 HIGH POC
8.8 Feb 15

Nagios XI version xi-5.7.5 is affected by OS command injection. Rated high severity (CVSS 8.8), this vulnerability is re

CVE-2021-25296 HIGH POC
8.8 Feb 15

Nagios XI version xi-5.7.5 is affected by OS command injection. Rated high severity (CVSS 8.8), this vulnerability is re

CVE-2021-25297 HIGH POC
8.8 Feb 15

Nagios XI version xi-5.7.5 is affected by OS command injection. Rated high severity (CVSS 8.8), this vulnerability is re

CVE-2012-6096 HIGH POC
7.5 Jan 22

Multiple stack-based buffer overflows in the get_history function in history.cgi in Nagios Core before 3.4.4, and Icinga

CVE-2013-1362 HIGH POC
7.5 Jul 09

Incomplete blacklist vulnerability in nrpc.c in Nagios Remote Plug-In Executor (NRPE) before 2.14 might allow remote att

CVE-2021-25299 MEDIUM POC
6.1 Feb 15

Nagios XI version xi-5.7.5 is affected by cross-site scripting (XSS). Rated medium severity (CVSS 6.1), this vulnerabili

CVE-2013-7108 MEDIUM POC
5.5 Jan 15

Multiple off-by-one errors in Nagios Core 3.5.1, 4.0.2, and earlier, and Icinga before 1.8.5, 1.9 before 1.9.4, and 1.10

CVE-2016-9565 CRITICAL POC
9.8 Dec 15

MagpieRSS, as used in the front-end component in Nagios Core before 4.2.2 might allow remote attackers to read or write

CVE-2018-15708 CRITICAL POC
9.8 Nov 14

Snoopy 1.0 in Nagios XI 5.5.6 allows remote unauthenticated attackers to execute arbitrary commands via a crafted HTTP r

CVE-2018-8734 CRITICAL POC
9.8 Apr 18

SQL injection vulnerability in the core config manager in Nagios XI 5.2.x through 5.4.x before 5.4.13 allows an attacker

CVE-2018-8733 CRITICAL POC
9.8 Apr 18

Authentication bypass vulnerability in the core config manager in Nagios XI 5.2.x through 5.4.x before 5.4.13 allows an

CVE-2021-37343 HIGH POC
8.8 Aug 13

A path traversal vulnerability exists in Nagios XI below version 5.8.5 AutoDiscovery component and could lead to post au

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy