CVE-2026-85183Taipy through 4.1.1 Cross-Site WebSocket Hijacking via Wildcard socket.io CORS
Updated under an hour ago ()
Does this affect you?
It affects Avaiga taipy. Add what you run to find out whether that includes you.
No exploitation reported and no EPSS estimate yet.
Do this next
Free account, 1 product
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.
- CVSS
- 9.3 CRITICAL (v3.1, CNA)CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N
- Weakness (CWE)
- CWE-1385
- Known exploited
- Not in CISA's KEV catalog
- EPSS (exploitation in the next 30 days)
- Not loaded for this CVE
- Assigned by
- VulnCheck
- NVD analysis
- Deferred
- Record last updated
- Sep 24, 2026
- First seen by InfoSec Signals
- Oct 9, 2026
Affected products
Avaiga taipy avaiga:taipy (from the name) | through 4.1.1 | CNA record |
References
- https://github.com/Avaiga/taipy/issues/2890issue-tracking
- https://github.com/Avaiga/taipyproduct
- https://github.com/Avaiga/taipy/blob/4.1.1/taipy/gui/server.pytechnical-description
- https://www.vulncheck.com/advisories/taipy-through-4.1.1-cross-site-websocket-hijacking-via-wildcard-socket-io-corsthird-party-advisory
The CVE record on cve.org NVD's entry
The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.