# CVE-2025-34323: Nagios Log Server < 2026R1.0.1 Local Privilege Escalation via Writable Scripts and Sudo Rules

> Local attackers can escalate privileges to root by replacing writable scripts executed via sudo, leading to full system compromise.

- **Severity:** High 8.5 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Nov 2025
- **Updated:** 14 May 2026
- **Also known as:** GHSA-m97c-3wp7-wp45

## What is CVE-2025-34323?

CVE-2025-34323 is a high-severity vulnerability in Nagios Log Server, published on 17 Nov 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Nagios Log Server versions prior to 2026R1.0.1 are vulnerable to local privilege escalation due to a combination of sudo misconfiguration and group-writable application directories. The 'www-data' user is a member of the 'nagios' group, which has write access to '/usr/local/nagioslogserver/scripts', while several scripts in this directory are owned by root and may be executed via sudo without a password. A local attacker running as 'www-data' can move one of these root-owned scripts to a backup name and create a replacement script with attacker-controlled content at the original path, then invoke it with sudo. This allows arbitrary commands to be executed with root privileges, providing full compromise of the underlying operating system.

Weakness: CWE-732 (Incorrect Permission Assignment for Critical Resource)

## Which versions are affected by CVE-2025-34323?

It affects 1 product.


Products: Nagios Log Server.

## How do I fix CVE-2025-34323?

No fix has been published for CVE-2025-34323 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-34323 being exploited?

There is no known exploitation of CVE-2025-34323 in the wild and no public exploit code.

## Other vulnerabilities in Nagios Log Server

- [CVE-2025-44823](https://insights.sbomify.com/CVE-2025-44823/): Information disclosure in Log Server (critical 9.9)
- [CVE-2025-34277](https://insights.sbomify.com/CVE-2025-34277/): Nagios Log Server < 2024R1.3.1 RCE via Malformed Dashboard ID (critical 9.4)
- [CVE-2025-34274](https://insights.sbomify.com/CVE-2025-34274/): Nagios Log Server < 2024R2.0.3 Logstash Process Root Privileges (critical 9.3)
- [CVE-2023-7322](https://insights.sbomify.com/CVE-2023-7322/): Nagios Log Server < 2024R1 Incorrect Authorization Granting Full API Access (high 8.7)
- [CVE-2025-34271](https://insights.sbomify.com/CVE-2025-34271/): Nagios Log Server < 2024R2.0.2 Cluster Manager Credential Requests Sent Over Plaintext (high 8.7)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-34323 and fix it if it is affected.

What it is: CVE-2025-34323 is a high-severity vulnerability in Nagios Log Server, published on 17 Nov 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-34323 in the wild and no public exploit code.

Affected product: Nagios Log Server. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-34323/ (Markdown: https://insights.sbomify.com/CVE-2025-34323/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-34323
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-34323
- OSV: https://osv.dev/vulnerability/CVE-2025-34323

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-34323/
Summaries are generated and may contain mistakes; the official description above is the record.