Skip to main content

Nagios Log Server CVE-2025-34298

HIGH
Improper Preservation of Permissions (CWE-281)
2025-10-30 disclosure@vulncheck.com
8.7
CVSS 4.0 · Vendor: vulncheck
View

Attack ChainAIDerived

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

  1. Access
    Authenticate as low-privileged user
  2. Delivery
    Submit invalid email in change workflow
  3. Exploit
    Trigger inconsistent account identity state
  4. Execution
    Gain elevated privileges / bypass access controls
  5. Impact
    Administrative control of Log Server

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Permission preservation
Exploitation Conditions

Attacker must hold a valid authenticated account on the Nagios Log Server instance (PR:L) and reach the per-user account email-change workflow; exploitation is triggered specifically by setting the account email to an invalid value, which the application fails to validate and uses to derive authorization state. LIMITING FACTORS: requires pre-existing authenticated (even if low-privileged) access, so it is not exploitable by fully unauthenticated outsiders; affected instances are those running Nagios Log Server versions prior to 2024R1.3.2 (2024 R1 through R1.3.1 per the CPE list); no special non-default configuration or user interaction from a victim is needed. No confirmed evidence of a prerequisite beyond authenticated access and access to the email-change feature.

Impact

This is a credible, above-average-priority issue but not a drop-everything emergency. The vendor-supplied CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:L/UI:N, VC:H/VI:H/VA:H, SC/SI/SA:N) scores 8.7 (High) and is internally consistent with the description: a network-reachable, low-complexity attack requiring only existing low-level authenticated access (PR:L), no user interaction, yielding full confidentiality/integrity/availability impact on the vulnerable system via privilege escalation - matching CWE-281 (improper preservation of permissions). The key tempering signals: exploitation requires an already-authenticated account (PR:L), so this is a privilege-escalation primitive for an insider or a foothold attacker, not a pre-auth remote takeover. On the exploitation-likelihood side there is NO EPSS score, NO CISA KEV listing, and NO public POC in the provided data - meaning no public exploit identified at time of analysis and no evidence of active exploitation. SSVC framing: exploitation status 'none observed', technical impact 'total' (full control of the Log Server), automatability likely 'no' because it needs a valid authenticated session per target. MISSING DATA: EPSS, KEV, and POC status are all absent from the input and cannot be inferred; the CVSS vector is vendor/VulnCheck-supplied (not independently confirmed by NVD as a reviewed score). Net: treat as a high-value escalation bug to patch promptly in any multi-user Nagios Log Server deployment, but real-world urgency is moderated by the authentication precondition and absence of known exploitation.

Exploit ScenarioDerived

A low-privileged but authenticated Nagios Log Server user navigates to their own account settings and submits an invalid email value through the email-change workflow. Because validation and authorization checks are tied to email-identity state, the account is left in an inconsistent state that the application interprets as holding elevated privileges, letting the user bypass intended access controls and gain administrative capabilities. No public exploit code is identified at time of analysis, so this would currently require an attacker to independently reproduce the email-state manipulation.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
No patch listed yet 0.7% exploitation probability (EPSS)

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

Alert me

AnalysisAIv1 – Oct 07, 2026

Privilege escalation in Nagios Log Server (versions 2024 R1 through 2024R1.3.1, and all releases prior to 2024R1.3.2) lets an authenticated user elevate their own privileges by abusing the account email-change workflow. Because the application fails to validate the submitted email value and appears to derive authorization state from the account's email identity, setting an invalid email value drives the account into an inconsistent state that bypasses intended access controls and grants elevated privileges. Exploitation requires a pre-existing valid account (authenticated, low-privilege is sufficient) and no victim interaction; there is no public exploit identified at time of analysis, and no CISA KEV listing, though the high CIA impact and low attack complexity make it an above-average-priority fix rather than a drop-everything emergency.

RemediationAI

Vendor-released patch: upgrade to Nagios Log Server 2024R1.3.2, which corrects the email-change validation and the authorization state derived from the account email; consult the Nagios changelog at https://www.nagios.com/changelog/nagios-log-server-2024r1/ and the VulnCheck advisory at https://www.vulncheck.com/advisories/nagios-log-server-set-email-privilege-escalation for the official guidance. Because exploitation requires only a valid low-privileged account and access to the per-user email-change workflow, prioritize patching any instance that exposes user self-service registration or a broad authenticated user base. Where immediate upgrade is not possible, compensating controls include restricting the email-change function to administrator-mediated changes (disabling user self-service email edits), auditing and alerting on email-field modification events and on accounts whose stored email is malformed or empty, and tightening role assignments so that no low-privileged group has any path to privileged role membership. Trade-offs: disabling self-service email changes increases administrative workload and can block legitimate password/notification recovery flows, and audit-only monitoring does not prevent the escalation itself - it only shortens detection time. Reviewing existing accounts for inconsistent identity state and forcing re-validation of stored emails after upgrading is also advisable, since accounts already left in an abnormal state may retain unexpected permissions.

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 root cause class is CWE-281 (Improper Preservation of Permissions): the account email-change workflow in Nagios Log Server does not correctly preserve or recompute the privilege and identity state associated with an account when the email value is modified. Nagios Log Server is a centralized log management/analytics product (Elasticsearch-based backend with a web UI and role-based access control), where the account email is treated as an identity attribute that feeds into authorization decisions. The flaw is that invalid email input is accepted without validation, and the resulting inconsistent identity state is then trusted by the authorization layer, allowing a low-privileged authenticated user to obtain elevated privileges or sidestep access controls. The CPE data confirms the affected line is the 2024 R1 release train (2024 R1, R1.0.1, R1.0.2, R1.1, R1.2, R1.3, R1.3.1, plus generic prior versions). The CVSS v4.0 vector (AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N) and the independent CVSS v3.1 assessment (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) agree that the attacker is network-reachable and authenticated, that no user interaction or non-default configuration is needed, and that the vulnerability is confined to the vulnerable component (no subsequent-system impact). Successful exploitation yields high confidentiality, integrity, and availability impact on the Log Server instance itself - effectively full compromise of the affected host's log data and configuration.

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 8.7 HIGH
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
vuln.today AI 8.8 HIGH

Network-reachable email-change workflow exploitable with a low-privileged authenticated account (PR:L) and no interaction; escalation yields full control of the system, and scope stays unchanged (SC/SI/SA:N).

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
None
Subsequent system: Integrity
None
Subsequent system: Availability
None

DescriptionCVE.org

Nagios Log Server versions prior to 2024R1.3.2 contain a privilege escalation vulnerability in the account email-change workflow. A user could set their own email to an invalid value and, due to insufficient validation and authorization checks tied to email identity state, trigger inconsistent account state that granted elevated privileges or bypassed intended access controls.

Executive ViewAI

Why It Matters

Nagios Log Server versions 2024 R1 through 2024R1.3.1 (and all releases before 2024R1.3.2) contain a high-severity privilege escalation flaw that lets any existing user account, including a low-privilege one, promote itself to a higher privilege level by submitting an invalid email address through the normal account email-change workflow. Because the platform is typically used to centralize and retain security and operational log data, an attacker who gains elevated rights could reach log content, configuration, and administrative functions that should be reserved for trusted administrators, undermining the integrity of the very audit trail relied upon for detection and compliance. Leadership should care because exploitation needs only a legitimate account and low complexity, meaning a single compromised or careless user credential, or a malicious insider, could silently expand access across a system whose trustworthiness underpins security monitoring and regulatory obligations; the absence of public exploit code and CISA KEV listing keeps this an above-average-priority hardening item rather than a drop-everything emergency.

Business Impact: High
Compensating Controls

No vendor-released patch identified at time of analysis. Interim mitigations: restrict platform access to the minimum necessary accounts and enforce least privilege with multi-factor authentication; disable or tightly control the self-service email-change functionality where configuration allows; audit all accounts for anomalous or invalid email values and inconsistent identity/privilege state and reset credentials on any suspect account; monitor and alert on email-change activity, privilege modifications, and administrative logins; and isolate Nagios Log Server on a segmented management network with restricted inbound access until a fixed version is available and applied.

Threat Intelligence Overview

EPSS Score
0.7%
Top 48% exploitable
Prevalence
Low
niche commercial log-management product within the Nagios monitoring suite
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 HIGH
CISA KEV No
Public POC No
EPSS 0.7%
Patch available No
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
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

45
Low Medium High Critical
KEV: 0
EPSS: +1
CVSS: +44
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Privilege escalation occurs when an attacker leverages flaws in access control mechanisms to gain permissions beyond what they were originally granted.

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:*:*:*:*:*:*
cpe:2.3:a:nagios:log_server:2024:r1.3.1:*:*:*:*:*:*

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