# CVE-2026-92800: Docs before 5.4.1 Stale Collaboration Session After Access Revocation

> Attackers with revoked access retain real-time read and write access to sub-documents via stale websocket sessions in Suitenumerique Docs.

- **Severity:** High 7.6 (`CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **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:** 16 Sep 2026
- **Updated:** 19 Sep 2026
- **Also known as:** GHSA-r6pv-x5p3-8fv6

## What is CVE-2026-92800?

CVE-2026-92800 is a high-severity missing authorization vulnerability in suitenumerique Docs, published on 16 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Docs before 5.4.1 fails to properly revoke websocket collaboration connections when access is revoked at parent documents. Attackers with revoked access can retain real-time read and write access to sub-documents through open websocket sessions that are never disconnected.

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

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


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

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

## Is CVE-2026-92800 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-92800 is a high-severity missing authorization vulnerability in suitenumerique Docs, published on 16 Sep 2026. 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-2026-92800 exists.

Affected product: suitenumerique Docs. 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-92800/ (Markdown: https://insights.sbomify.com/CVE-2026-92800/index.md)
```

## Sources

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

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