{"description":"Trending threats, MITRE ATT\u0026CK coverage, and detection metadata. Fed continuously.","feed_url":"https://feed.craftedsignal.io/tags/taipy/feed.json","home_page_url":"https://feed.craftedsignal.io/","items":[{"_cs_actors":["jackfromeast"],"_cs_cpes":[],"_cs_cves":[],"_cs_exploited":false,"_cs_has_poc":false,"_cs_poc_references":[],"_cs_products":["Taipy (4.0.3)"],"_cs_severities":["high"],"_cs_tags":["cve-2025-30374","rce","class-pollution","taipy","python"],"_cs_type":"threat","_cs_vendors":["Avaiga"],"content_html":"\u003cp\u003eA severe class pollution vulnerability, identified as CVE-2025-30374, exists in Taipy v4.0.3. The vulnerability stems from an insecure recursive state update mechanism in \u003ccode\u003etaipy/gui/utils/_attributes.py\u003c/code\u003e, where client-provided input is used to dynamically update object attributes without validation. Attackers can leverage this to inject malicious attribute paths (analogous to prototype pollution), effectively overwriting internal application state, module attributes, or class methods at runtime.\u003c/p\u003e\n\u003cp\u003eThe impact is significant, as attackers can achieve Remote Code Execution (RCE) by manipulating the \u003ccode\u003eGui.__SELF_VAR\u003c/code\u003e attribute used within internal \u003ccode\u003eeval()\u003c/code\u003e calls. Furthermore, the vulnerability enables credential exfiltration, such as OpenAI API tokens, by redirecting outbound application traffic, as well as enabling Reflected XSS and Denial of Service (DoS) by crashing the application or injecting malicious content into rendered responses. This flaw represents a critical security risk for any Taipy deployment exposing application state management to client-side input.\u003c/p\u003e\n\u003ch2 id=\"attack-chain\"\u003eAttack Chain\u003c/h2\u003e\n\u003col\u003e\n\u003cli\u003eAttacker establishes a WebSocket connection to the targeted Taipy application.\u003c/li\u003e\n\u003cli\u003eAttacker crafts a malicious message payload containing an attribute path injection string (e.g., \u003ccode\u003e_TpN_tpec_TpExPr...\u003c/code\u003e).\u003c/li\u003e\n\u003cli\u003eThe message is sent to the Taipy server, where it is processed by \u003ccode\u003e_manage_message\u003c/code\u003e.\u003c/li\u003e\n\u003cli\u003eThe \u003ccode\u003e_setscopeattr_drill\u003c/code\u003e function is triggered, passing the attacker's input to the recursive \u003ccode\u003e_attrsetter\u003c/code\u003e function.\u003c/li\u003e\n\u003cli\u003eThe \u003ccode\u003e_attrsetter\u003c/code\u003e function uses \u003ccode\u003esetattr\u003c/code\u003e and \u003ccode\u003egetattr\u003c/code\u003e to traverse and modify server-side object attributes based on the attacker's path.\u003c/li\u003e\n\u003cli\u003eAttacker targets specific internal attributes such as \u003ccode\u003eGui.__SELF_VAR\u003c/code\u003e or method attributes on \u003ccode\u003e_TaipyBase\u003c/code\u003e.\u003c/li\u003e\n\u003cli\u003eUpon subsequent application logic execution, the modified attributes are accessed or evaluated (e.g., via \u003ccode\u003eeval()\u003c/code\u003e).\u003c/li\u003e\n\u003cli\u003eFinal objective achieved: RCE, credential exfiltration, XSS injection, or application crash.\u003c/li\u003e\n\u003c/ol\u003e\n\u003ch2 id=\"impact\"\u003eImpact\u003c/h2\u003e\n\u003cp\u003eThe vulnerability affects Taipy v4.0.3 users. Successful exploitation allows for complete server compromise through RCE, theft of sensitive configuration secrets like OpenAI tokens, disruption of services via DoS, and potential account takeover via XSS. Given the availability of public proof-of-concept exploits, the risk to unpatched infrastructure is high.\u003c/p\u003e\n\u003ch2 id=\"recommendation\"\u003eRecommendation\u003c/h2\u003e\n\u003cp\u003ePrioritize the following actions to detect and mitigate CVE-2025-30374:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003eUpdate Taipy to a patched version immediately upon vendor release.\u003c/li\u003e\n\u003cli\u003eImplement strict server-side validation for all input parameters received via WebSocket messages in \u003ccode\u003e_manage_message\u003c/code\u003e.\u003c/li\u003e\n\u003cli\u003eBlock or inspect WebSocket traffic containing deeply nested attribute paths or sequences targeting internal application classes.\u003c/li\u003e\n\u003cli\u003eAudit infrastructure logs for unauthorized WebSocket messages containing \u003ccode\u003e__class__\u003c/code\u003e, \u003ccode\u003e__base__\u003c/code\u003e, or \u003ccode\u003e__SELF_VAR\u003c/code\u003e patterns.\u003c/li\u003e\n\u003c/ul\u003e\n","date_modified":"2026-08-05T21:29:20Z","date_published":"2026-08-05T21:29:20Z","id":"https://feed.craftedsignal.io/briefs/2026-08-taipy-class-pollution/","summary":"Taipy v4.0.3 contains a class pollution vulnerability (CVE-2025-30374) that allows unauthenticated attackers to manipulate server-side state via crafted WebSocket messages, resulting in RCE, credential leakage, XSS, and DoS.","title":"Taipy Class Pollution Vulnerability Leading to RCE","url":"https://feed.craftedsignal.io/briefs/2026-08-taipy-class-pollution/"}],"language":"en","title":"CraftedSignal Threat Feed - Taipy","version":"https://jsonfeed.org/version/1.1"}