CVE-2026-48544: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') in Avaiga taipy
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.
AI Analysis
Technical Summary
CVE-2026-48544 describes a path traversal vulnerability in Avaiga taipy 4.1.1 within the ElementLibrary.get_resource() method (taipy/gui/extension/library.py). The vulnerability stems from an incomplete path containment check that uses str.startswith() without a trailing path separator, allowing crafted GET requests with path traversal sequences to escape the intended module directory. Flask's and Werkzeug's handling of path segments preserves traversal sequences, which bypass the flawed startswith check, enabling unauthorized file access outside the library directory. The issue is fixed in commit 129fd40, but no official patch release or advisory details are currently available.
Potential Impact
An unauthenticated attacker can exploit this vulnerability to access files outside the intended restricted directory, potentially exposing sensitive information or configuration files. The CVSS 4.0 score of 8.7 indicates a high severity with network attack vector, no privileges or user interaction required, and high impact on confidentiality. There is no indication of known exploits in the wild at this time.
Mitigation Recommendations
A fix is available in the codebase as of commit 129fd40. However, no official patch release or vendor advisory has been published yet. Users should apply the fix from the referenced commit or monitor the vendor's channels for an official patch. Until then, consider restricting access to the affected endpoint or implementing additional access controls to mitigate unauthorized file access.
CVE-2026-48544: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') in Avaiga taipy
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.
CVSS v4.0
Score 8.7high
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-48544 describes a path traversal vulnerability in Avaiga taipy 4.1.1 within the ElementLibrary.get_resource() method (taipy/gui/extension/library.py). The vulnerability stems from an incomplete path containment check that uses str.startswith() without a trailing path separator, allowing crafted GET requests with path traversal sequences to escape the intended module directory. Flask's and Werkzeug's handling of path segments preserves traversal sequences, which bypass the flawed startswith check, enabling unauthorized file access outside the library directory. The issue is fixed in commit 129fd40, but no official patch release or advisory details are currently available.
Potential Impact
An unauthenticated attacker can exploit this vulnerability to access files outside the intended restricted directory, potentially exposing sensitive information or configuration files. The CVSS 4.0 score of 8.7 indicates a high severity with network attack vector, no privileges or user interaction required, and high impact on confidentiality. There is no indication of known exploits in the wild at this time.
Mitigation Recommendations
A fix is available in the codebase as of commit 129fd40. However, no official patch release or vendor advisory has been published yet. Users should apply the fix from the referenced commit or monitor the vendor's channels for an official patch. Until then, consider restricting access to the affected endpoint or implementing additional access controls to mitigate unauthorized file access.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- VulnCheck
- Date Reserved
- 2026-05-21T18:34:46.417Z
- Cvss Version
- 4.0
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a170b58e29bf47b50c9071e
Added to database: 05/27/2026, 15:18:48 UTC
Last enriched: 07/15/2026, 10:04:49 UTC
Last updated: 07/31/2026, 19:22:59 UTC
Views: 41
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.