Cross-directory file access via lexical prefix check
Published Jun 10, 2026 · Updated Jun 10, 2026
Path traversal in Fission's fetcher and builder before 1.25.0 allows local users to read or write files outside an intended safe directory. SanitizeFilePath in pkg/utils/utils.go uses strings.HasPrefix without enforcing a path-separator boundary, so similarly prefixed sibling directories pass validation. Exploitation requires low-privileged Kubernetes access and prior creation or control of a sibling directory on the shared fetcher or builder volume.
Summary
What happened
Path traversal in Fission's fetcher and builder before 1.25.0 allows local users to read or write files outside an intended safe directory. SanitizeFilePath in pkg/utils/utils.go uses strings.HasPrefix without enforcing a path-separator boundary, so similarly prefixed sibling directories pass validation. Exploitation requires low-privileged Kubernetes access and prior creation or control of a sibling directory on the shared fetcher or builder volume.
The record
- CVE
- CVE-2026-50568
- Published
- Jun 10, 2026
- Updated
- Jun 10, 2026
- Vendor
- Fission
- Product
- Fission
- Classifications
- CWE-41, T1005
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 10, 2026CVE publishedPublication date reported by the CVE source.
- Jun 10, 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=< 1.25.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
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
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