# CVE-2025-28132: Auth bypass in n/a

> Attackers can reuse session tokens after logout to impersonate users and take over accounts in Nagios Network Analyzer.

- **Severity:** Medium 4.6 (`CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:L/I:L/A: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:** 1 Apr 2025
- **Updated:** 1 Apr 2025
- **Also known as:** GHSA-qrfj-w3wq-p623

## What is CVE-2025-28132?

CVE-2025-28132 is a medium-severity authentication bypass vulnerability in n/a, published on 1 Apr 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A session management flaw in Nagios Network Analyzer 2024R1.0.3 allows an attacker to reuse session tokens even after a user logs out, leading to unauthorized access and account takeover. This occurs due to insufficient session expiration, where session tokens remain valid beyond logout, allowing an attacker to impersonate users and perform actions on their behalf.

Weakness: CWE-613 (DEPRECATED: Insufficient Session Expiration)

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

It affects 1 product.


Products: Nagios Nagios Network Analyzer.

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

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

## Is CVE-2025-28132 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-28132 is a medium-severity authentication bypass vulnerability in n/a, published on 1 Apr 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-28132 in the wild and no public exploit code.

Affected product: n/a. 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-28132/ (Markdown: https://insights.sbomify.com/CVE-2025-28132/index.md)
```

## Sources

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

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