{"answers":{"affected":"3 open source packages ship an affected version, including github.com/fission/fission.","exploited":"There is no known exploitation of CVE-2026-50568 in the wild and no public exploit code.","fix":"Upgrade github.com/fission/fission to 1.25.0 or later.","what":"CVE-2026-50568 is a low-severity path traversal vulnerability in fission, published on 10 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-50568 and fix it if it is affected.\n\nWhat it is: CVE-2026-50568 is a low-severity path traversal vulnerability in fission, published on 10 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-50568 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- github.com/fission/fission (Go): affected all versions; fixed in 1.25.0\n- github.com/fission/fission (Go): affected all versions; fixed in 1.25.0\n- github.com/fission/fission (Go): affected all versions; fixed in 1.25.0\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-50568/ (Markdown: https://insights.sbomify.com/CVE-2026-50568/index.md)","id":"CVE-2026-50568","markdown":"https://insights.sbomify.com/CVE-2026-50568/index.md","name":"CVE-2026-50568","record":{"aliases":["GHSA-r5jh-q2mw-gcx4","GO-2026-6130"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Kubernetes serverless framework","requires_auth":"low_privilege","summary":"Attackers can escape intended directories via lexical prefix bypass, enabling unauthorized file reads or writes in Fission serverless framework.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":3.6,"severity":"low","source":"cna","vector":"CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-41","name":"Improper Resolution of Path Equivalence"}],"description":"Fission is an open-source, Kubernetes-native serverless framework that simplifies the deployment of functions and applications on Kubernetes. Prior to version 1.25.0, SanitizeFilePath in pkg/utils/utils.go validated that a path stayed under a safe directory by calling strings.HasPrefix(path, safedir). This is a lexical check, not a directory boundary check: /packages-extra/evil starts with /packages, so it passed. The function did not enforce a path-separator boundary, so any sibling directory whose name began with the safe-directory string was accepted. Callers included the builder's Clean handler (pkg/builder/builder.go:208) and the fetcher's Fetch / Upload handlers (pkg/fetcher/fetcher.go). A tenant who could pre-create or control a sibling directory under the fetcher / builder's shared volume could induce a write or read outside the intended safe directory. This issue has been patched in version 1.25.0.","ecosystems":["Go"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Fission: SanitizeFilePath lexical HasPrefix bypass permits sibling-directory escape","id":"CVE-2026-50568","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Go","product":null,"products":[],"type":"path_traversal","year":"2026"},"n_packages":3,"n_references":4,"next":{"headline":"Fission: HTTPTrigger admission omits RelativeURL / Prefix validation; kubectl apply bypasses CLI checks","id":"CVE-2026-50569"},"packages":[{"ecosystem":"Go","fixed":["1.25.0"],"introduced":["0"],"last_affected":[],"package":"github.com/fission/fission","purl":null,"source":"GHSA-r5jh-q2mw-gcx4"},{"ecosystem":"Go","fixed":["1.25.0"],"introduced":["0"],"last_affected":[],"package":"github.com/fission/fission","purl":"pkg:golang/github.com/fission/fission","source":"GHSA-r5jh-q2mw-gcx4"},{"ecosystem":"Go","fixed":["1.25.0"],"introduced":["0"],"last_affected":[],"package":"github.com/fission/fission","purl":"pkg:golang/github.com/fission/fission","source":"GO-2026-6130"}],"prev":{"headline":"Fission: Zip Slip in pkg/utils/zip.go:Unarchive allows fetcher to write outside the destination directory","id":"CVE-2026-50567"},"products":["fission"],"published":"2026-06-10","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"Go Vulnerability Database","prefix":"GO"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-06-11","vendors":["fission"]},"summary":"Attackers can escape intended directories via lexical prefix bypass, enabling unauthorized file reads or writes in Fission serverless framework.","url":"https://insights.sbomify.com/CVE-2026-50568/"}