# CVE-2026-108689: Wukong AICRM through 20260610 Authorization Bypass via User-Controlled Session ID in POST /chat/send

> Authenticated attackers can access and modify other users' AI chat sessions by manipulating session IDs, leading to data disclosure and integrity loss.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/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:** 11 Oct 2026
- **Updated:** 18 Oct 2026
- **Also known as:** GHSA-2p74-f492-56xr

## What is CVE-2026-108689?

CVE-2026-108689 is a medium-severity missing authorization vulnerability in WuKongOpenSource Wukong AICRM, published on 11 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Wukong AICRM through 20260610 contains a missing authorization vulnerability that allows authenticated users to write into other users' AI chat sessions by supplying an arbitrary sessionId to POST /chat/send. Attackers can append messages to a victim's conversation and receive streamed assistant replies built from the victim's last 20 messages, disclosing conversation content.

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

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


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

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

## Is CVE-2026-108689 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-108689 is a medium-severity missing authorization vulnerability in WuKongOpenSource Wukong AICRM, published on 11 Oct 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-108689 exists.

Affected product: WuKongOpenSource Wukong AICRM. 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-108689/ (Markdown: https://insights.sbomify.com/CVE-2026-108689/index.md)
```

## Sources

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

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