Path traversal via URI segment overflow
Published Sep 11, 2026 · Updated Sep 15, 2026
Path traversal in libks before 2.0.11 allows remote attackers to preserve parent-directory segments in crafted HTTP request URIs. clean_uri() exceeds its internal path-segment canonicalization capacity and passes the URI through with embedded parent-directory sequences intact. Exposure requires a consumer to accept the request and join the resulting URI to a filesystem path, enabling access outside the intended path boundary.
Summary
What happened
Path traversal in libks before 2.0.11 allows remote attackers to preserve parent-directory segments in crafted HTTP request URIs. clean_uri() exceeds its internal path-segment canonicalization capacity and passes the URI through with embedded parent-directory sequences intact. Exposure requires a consumer to accept the request and join the resulting URI to a filesystem path, enabling access outside the intended path boundary.
The record
- CVE
- CVE-2026-49846
- Published
- Sep 11, 2026
- Updated
- Sep 15, 2026
- Vendor
- SignalWire
- Product
- libks
- Classifications
- Unavailable
- Attack vector
- network
- Privileges
- Unavailable
Timeline
How it unfolded
- Sep 11, 2026CVE publishedPublication date reported by the CVE source.
- Sep 15, 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=< 2.0.11
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
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
No sourced classifications are available.
Public exploit references
No public exploit references are available in this record.
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