VulnerabilityPublished 30 Oct 2025Updated 17 Nov 2025

CVE-2025-34272: Nagios Log Server · Information Exposure

Affects Nagios Log ServerSource CVE Database V5

Not known to be exploited · CVSS 5.3 Medium.

Data as of 26 Oct 2026, 12:55 UTC

CVSS 4.0 base score

5.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.8% chance of exploitation in 30 days – higher than 58% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: Low
User Interaction: None
Vulnerable system confidentiality: Low
Vulnerable system integrity: None
Vulnerable system availability: None
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: Low: The attacker requires privileges that provide basic capabilities that are typically limited to settings and resources owned by a single low-privileged user. Alternatively, an attacker with Low privileges has the ability to access only non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the Vulnerable System.
Vulnerable system integrity: None: There is no loss of integrity within the Vulnerable System.
Vulnerable system availability: None: There is no impact to availability within the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 30 Oct 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Nagios Log Server	Affected =0	Fixed in–

AI-suggested

The primary mitigation is to upgrade Nagios Log Server to version 2024R2.0.3 or later, where the fallback logic for deleted default dashboards has been corrected to prevent exposure. Organizations should audit their current dashboard sharing and access control policies to ensure that dashboards are not overly permissive and that sensitive information is appropriately segmented. Implement strict role-based access controls (RBAC) and minimize dashboard sharing to only necessary users. Regularly review user permissions and dashboard configurations to detect and remediate any unintended access. Additionally, monitor logs for unusual access patterns to dashboards that could indicate exploitation attempts. Employ network segmentation and firewall rules to limit access to Nagios Log Server interfaces to trusted administrative networks. Finally, incorporate this vulnerability into vulnerability management and patching cycles to ensure timely updates and reduce exposure windows.

Description

CVE-2025-34272 is a medium-severity vulnerability in Nagios Log Server versions prior to 2024R2.0.3. When a user's configured default dashboard is deleted, the application may incorrectly display another user's dashboard as the default, potentially exposing sensitive information or privileges. This occurs due to improper fallback handling in the dashboard selection logic. The vulnerability does not require user interaction or authentication beyond low privileges, and it can be exploited remotely over the network. Although no known exploits are currently in the wild, affected organizations should prioritize patching to prevent unauthorized data exposure. European organizations using Nagios Log Server for log management and monitoring are at risk, especially those with complex dashboard sharing policies. Countries with high adoption of Nagios products and critical infrastructure monitoring are more likely to be targeted. Mitigation involves updating to version 2024R2.

Impact

For European organizations, the exposure of sensitive information through this vulnerability could lead to unauthorized disclosure of operational, security, or business-critical data contained within Nagios Log Server dashboards. This may include log data, monitoring alerts, or configuration details that could aid attackers in reconnaissance or lateral movement. Organizations in sectors such as finance, energy, telecommunications, and government—where Nagios Log Server is commonly used for infrastructure monitoring—face increased risk. The unintended privilege exposure could also allow lower-privileged users to gain insights or access beyond their authorization, potentially violating data protection regulations such as GDPR. This could result in regulatory penalties, reputational damage, and operational disruptions. Since the vulnerability can be exploited remotely without authentication or user interaction, it increases the attack surface and risk of automated exploitation attempts. Although no exploits are currently known, the medium severity score and ease of exploitation warrant proactive remediation to protect sensitive monitoring data and maintain compliance with European cybersecurity standards.

Summary

CVE-2025-34272 is a vulnerability classified under CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor) affecting Nagios Log Server versions prior to 2024R2.0.3. The issue arises when a user’s configured default dashboard is deleted; instead of falling back to an empty or neutral default dashboard, the system may present an unexpected dashboard as the user's default view. This unexpected dashboard could belong to another user or contain information that the current user should not have access to, depending on the dashboard sharing and access control policies configured in the product. The vulnerability stems from improper handling of dashboard state fallback logic within the application. The CVSS 4.0 base score is 5.3 (medium severity), with attack vector being network-based (AV:N), low attack complexity (AC:L), no authentication required (AT:N), and no user interaction needed (UI:N). The vulnerability impacts confidentiality primarily, with limited impact on integrity or availability. No known exploits have been reported in the wild as of now. The vulnerability affects all deployments of Nagios Log Server prior to the fixed version 2024R2.0.3, which is designed to ensure a reliable fallback to an empty default dashboard, preventing unauthorized exposure of dashboards and their contained data. This vulnerability is particularly relevant in environments where dashboards contain sensitive operational or security data and where dashboard sharing policies are permissive or complex.

CWE-200Exposure of Sensitive Information to an Unauthorized Actor (opens in a new tab)
Class weaknessLikelihood of exploit: HighCWE Top 25 (2025): #20OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.
MITRE discourages mapping vulnerabilities to this broad entry; the root cause is usually a more specific weakness.
Architecture and Design · Separation of Privilege
Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area.
OWASP Cheat Sheets
Error Handling (opens in a new tab)
Logging (opens in a new tab)
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V8.3.4 (opens in a new tab)
V14.3.3 (opens in a new tab)
V7.3.3 (opens in a new tab)
Attack patterns
Subverting Environment Variable Values (opens in a new tab)
ICMP Echo Request Ping (opens in a new tab)
TCP SYN Scan (opens in a new tab)
Enumerate Mail Exchange (MX) Records (opens in a new tab)
DNS Zone Transfers (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 24 Nov 2025, 22:19 UTC

WeaknessesCWE-200

Technical details

References

Community reviews

Related threats