# CVE-2025-44824: Missing authorization in Log Server

> Authenticated read-only users can stop the Elasticsearch service, causing denial of service, despite API error messages.

- **Severity:** High 8.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:L/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Oct 2025
- **Updated:** 8 Oct 2025
- **Also known as:** GHSA-mh3w-pwxw-972f

## What is CVE-2025-44824?

CVE-2025-44824 is a high-severity missing authorization vulnerability in Nagios Log Server, published on 7 Oct 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Nagios Log Server before 2024R1.3.2 allows authenticated users (with read-only API access) to stop the Elasticsearch service via a /nagioslogserver/index.php/api/system/stop?subsystem=elasticsearch call. The service stops even though "message": "Could not stop elasticsearch" is in the API response. This is GL:NLS#474.

Weakness: CWE-863 (Incorrect Authorization)

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

It affects 1 product.


Products: Nagios Log Server.

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

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

## Is CVE-2025-44824 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-44824 exists.

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

What it is: CVE-2025-44824 is a high-severity missing authorization vulnerability in Nagios Log Server, published on 7 Oct 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-44824 exists.

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-44824/ (Markdown: https://insights.sbomify.com/CVE-2025-44824/index.md)
```

## Sources

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

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