# CVE-2026-111169: La Suite Docs through 6.0.1 Authorization Bypass via Comment Thread Creation

> Authenticated attackers can inject comments into unauthorized document threads by manipulating resource IDs, compromising data integrity.

- **Severity:** Low 2.3 (`CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:N/VC:N/VI:L/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:** 15 Oct 2026
- **Updated:** 26 Oct 2026
- **Also known as:** GHSA-pxmx-2p3q-jfwf

## What is CVE-2026-111169?

CVE-2026-111169 is a low-severity missing authorization vulnerability in suitenumerique docs, published on 15 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

La Suite Docs through 6.0.1 contains an authorization bypass vulnerability that allows authenticated users to write comments into threads of documents they cannot access. Attackers who know a thread UUID can route a POST comment request through their own document's resource_id, inserting comments into another document's thread without access.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

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


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

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

## Is CVE-2026-111169 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-111169 is a low-severity missing authorization vulnerability in suitenumerique docs, published on 15 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-111169 in the wild and no public exploit code.

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

## Sources

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

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