# CVE-2026-129280: Multiple ServerUI and ServerUI2 SOAP operations in N-able N-central before 2026.4.1 HF3 do not verify the caller's session, permissions or customer scope.


- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:L/SI:L/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 17 Nov 2026
- **Updated:** 17 Nov 2026
- **Also known as:** GHSA-cgxh-3hhc-m5w6

## What is CVE-2026-129280?

CVE-2026-129280 is a critical vulnerability in N-able N-central, published on 17 Nov 2026. 

### Official description

Multiple ServerUI and ServerUI2 SOAP operations in N-able N-central before 2026.4.1 HF3 do not verify the caller's session, permissions or customer scope. A remote attacker, in some cases without authentication, can read device and patch data, test passwords of user accounts, send messages to managed agents, and modify device and service settings belonging to other customers.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2026-129280?


## How do I fix CVE-2026-129280?

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

## Is CVE-2026-129280 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-129280 and fix it if it is affected.

What it is: CVE-2026-129280 is a critical vulnerability in N-able N-central, published on 17 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-129280 in the wild and no public exploit code.

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

## Sources

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

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