Unauthenticated file disclosure via prefix-only containment check
Published May 27, 2026 · Updated May 27, 2026
Path traversal in Avaiga Taipy 4.1.1 and earlier allows remote attackers to read files outside an extension library directory. ElementLibrary.get_resource() resolves the requested path but uses str.startswith() for containment, accepting a prefix-matching sibling path. The unauthenticated extension-resource route exposes existing sibling files when crafted GET paths retain traversal segments.
Summary
What happened
Path traversal in Avaiga Taipy 4.1.1 and earlier allows remote attackers to read files outside an extension library directory. ElementLibrary.get_resource() resolves the requested path but uses str.startswith() for containment, accepting a prefix-matching sibling path. The unauthenticated extension-resource route exposes existing sibling files when crafted GET paths retain traversal segments.
The record
- CVE
- CVE-2026-48544
- Published
- May 27, 2026
- Updated
- May 27, 2026
- Vendor
- Avaiga
- Product
- Taipy
- Classifications
- CWE-22, T1005
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 27, 2026CVE publishedPublication date reported by the CVE source.
- May 27, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=4.1.1
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Taipy extension-resource path traversal proof of conceptfunctional · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo