# CVE-2025-9316: N-central unauthenticated sessionID generation

> Attackers can generate session IDs for unauthenticated users, bypassing authentication controls in N-central.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Nov 2025
- **Updated:** 12 Nov 2025
- **Also known as:** GHSA-9vwr-g237-h5c9

## What is CVE-2025-9316?

CVE-2025-9316 is a medium-severity authentication bypass vulnerability in N-able N-central, published on 12 Nov 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

N-central < 2025.4 can generate sessionIDs for unauthenticated users

This issue affects N-central: before 2025.4.

Weakness: CWE-1284 (Improper Validation of Specified Quantity in Input)

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


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

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

## Is CVE-2025-9316 being exploited?

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

Public exploit code:

- Proof of concept exploit for N-able N-central to chain CVE-2025-9316 and CVE-2025-11700 to read files (github_poc): https://github.com/horizon3ai/n-able_n-central_xxe_file_read
- N-able N-Central Authentication Bypass and XXE Scanner (metasploit)
- https://github.com/zyyyys123/CVE-2025-9316_CVE-2025-11700 (github_poc): https://github.com/zyyyys123/CVE-2025-9316_CVE-2025-11700
- N-central - Authentication Bypass (nuclei): http/cves/2025/CVE-2025-9316.yaml

## Fix prompt for AI coding agents

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

What it is: CVE-2025-9316 is a medium-severity authentication bypass vulnerability in N-able N-central, published on 12 Nov 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-9316 exists.

Affected product: N-able N-central. 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-9316/ (Markdown: https://insights.sbomify.com/CVE-2025-9316/index.md)
```

## Sources

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

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