CVE-2026-48544: Avaiga taipy · Path Traversal
Affects Avaiga taipySource CVE Database V5
Not known to be exploited · CVSS 8.7 High.
Data as of 30 Oct 2026, 11:52 UTC
- EPSS
- 0.5% chance of exploitation in 30 days – higher than 44% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 27 May 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Avaigataipy | Affected
| Fixed in– |
PyPItaipypkg:pypi/taipyOther threats | Affected
| Fixed in– |
GitHubtaipypkg:github/taipyOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A fix for this vulnerability is available and was introduced after version 4.1.1 in commit 129fd40. Users should upgrade to a version that includes this fix to prevent exploitation. Until patched, avoid exposing the vulnerable endpoint to untrusted networks or users.
Description
Taipy 4.1.1, fixed in commit 129fd40, contains a path traversal vulnerability in the ElementLibrary.get_resource() method in taipy/gui/extension/library.py that allows unauthenticated attackers to escape the intended module directory by exploiting an incomplete path containment check using str.startswith() without a trailing path separator. Attackers can send crafted GET requests with path traversal segments targeting a prefix-matching sibling directory on disk, bypassing the directory containment check because Flask's path converter and Werkzeug's WSGI layer preserve the traversal segments while the resolved path still satisfies the flawed startswith comparison, enabling unauthorized file access outside the intended library directory.
References
- github.com/Avaiga/taipy/issues/2868 (opens in a new tab)
- github.com/Avaiga/taipy/pull/2871 (opens in a new tab)
- github.com/Avaiga/taipy/commit/129fd407ffca49ee4ab853772c88d0c873e038dd (opens in a new tab)
- vulncheck.com/advisories/taipy-path-traversal-via-elementlibrary-get-resource (opens in a new tab)