# CVE-2025-34322: Nagios Log Server < 2026R1.0.1 Authenticated Command Injection via Natural Language Queries

> Authenticated attackers can execute arbitrary commands on Nagios Log Server hosts by exploiting unsanitized inputs in the experimental Natural Language Queries feature.

- **Severity:** High 8.6 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Nov 2025
- **Updated:** 14 May 2026
- **Also known as:** GHSA-qrg4-jqvv-5724

## What is CVE-2025-34322?

CVE-2025-34322 is a high-severity command injection vulnerability in Nagios Log Server, published on 17 Nov 2025. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Nagios Log Server versions prior to 2026R1.0.1 contain an authenticated command injection vulnerability in the experimental 'Natural Language Queries' feature. When this feature is configured, certain user-controlled settings—including model selection and connection parameters—are read from the global configuration and concatenated into a shell command that is executed via shell_exec() without proper input handling or command-line argument sanitation. An authenticated user with access to the 'Global Settings' page can supply crafted values in these fields to inject additional shell commands, resulting in arbitrary command execution as the 'www-data' user and compromise of the Log Server host.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

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

It affects 1 product.


Products: Nagios Log Server.

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

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

## Is CVE-2025-34322 being exploited?

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

Public exploit code:

- Proof of Concept exploits for CVE-2025-34322 and CVE-2025-34323 in Nagios Log Server (github_poc): https://github.com/mcorybillington/CVE-2025-34322_CVE-2025-34323_Nagios_Log_Server

## 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-34322 and fix it if it is affected.

What it is: CVE-2025-34322 is a high-severity command injection vulnerability in Nagios Log Server, published on 17 Nov 2025. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-34322 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-34322/ (Markdown: https://insights.sbomify.com/CVE-2025-34322/index.md)
```

## Sources

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

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