# CVE-2026-85183: Taipy through 4.1.1 Cross-Site WebSocket Hijacking via Wildcard socket.io CORS

> Attackers can hijack WebSocket sessions to modify application state and trigger actions due to insecure CORS configuration in Taipy.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:N/SC:H/SI:H/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 3 Sep 2026
- **Updated:** 24 Sep 2026
- **Also known as:** GHSA-jcr8-jmf2-43vw

## What is CVE-2026-85183?

CVE-2026-85183 is a critical vulnerability in Avaiga taipy, published on 3 Sep 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Taipy configures its socket.io server with wildcard CORS origin and credential flag enabled, allowing any web page to establish credentialed WebSocket connections to victim applications. Attackers can open socket.io sessions from arbitrary domains and invoke state variable modifications and action callbacks without CSRF protection.

Weakness: CWE-1385 (Missing Origin Validation in WebSockets)

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


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

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

## Is CVE-2026-85183 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-85183 is a critical vulnerability in Avaiga taipy, published on 3 Sep 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-85183 exists.

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

## Sources

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

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