{"answers":{"affected":"3 open source packages ship an affected version, including github.com/fission/fission.","exploited":"There is no known exploitation of CVE-2026-50569 in the wild and no public exploit code.","fix":"Upgrade github.com/fission/fission to 1.25.0 or later.","what":"CVE-2026-50569 is a medium-severity missing authorization vulnerability in fission, published on 10 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-50569 and fix it if it is affected.\n\nWhat it is: CVE-2026-50569 is a medium-severity missing authorization vulnerability in fission, published on 10 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-50569 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-50569/ (Markdown: https://insights.sbomify.com/CVE-2026-50569/index.md)","id":"CVE-2026-50569","markdown":"https://insights.sbomify.com/CVE-2026-50569/index.md","name":"CVE-2026-50569","record":{"aliases":["GHSA-vchh-r53j-8mpw","GO-2026-6131"],"analysis":{"component_type":"cloud_service","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Kubernetes serverless framework","requires_auth":"low_privilege","summary":"Attackers can bypass URL validation checks in Fission HTTPTriggers by using kubectl or direct API calls instead of the CLI, potentially violating security policies.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":4.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-20","name":"Improper Input Validation"}],"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, HTTPTriggerSpec.Validate() validated Methods, FunctionReference, Host, IngressConfig, and CorsConfig, but silently skipped RelativeURL and Prefix. Those two fields were validated at the CLI level only (pkg/fission-cli/cmd/httptrigger/create.go:83). The post-CRD-modernization webhook for HTTPTrigger was retired in favor of API-server CEL — and CEL had no rules on those fields either — so an HTTPTrigger created via kubectl apply or a direct Kubernetes REST API call bypassed every URL-level check. 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: HTTPTrigger admission omits RelativeURL / Prefix validation; kubectl apply bypasses CLI checks","id":"CVE-2026-50569","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Go","product":null,"products":[],"type":"missing_authorization","year":"2026"},"n_packages":3,"n_references":3,"next":{"headline":"Fission: Incomplete capability denylist in Environment/Function PodSpec validation allows tenant-added CAP_SYS_TIME and cross-tenant node wall-clock corruption","id":"CVE-2026-50570"},"packages":[{"ecosystem":"Go","fixed":["1.25.0"],"introduced":["0"],"last_affected":[],"package":"github.com/fission/fission","purl":null,"source":"GHSA-vchh-r53j-8mpw"},{"ecosystem":"Go","fixed":["1.25.0"],"introduced":["0"],"last_affected":[],"package":"github.com/fission/fission","purl":"pkg:golang/github.com/fission/fission","source":"GHSA-vchh-r53j-8mpw"},{"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-6131"}],"prev":{"headline":"Fission: SanitizeFilePath lexical HasPrefix bypass permits sibling-directory escape","id":"CVE-2026-50568"},"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-10","vendors":["fission"]},"summary":"Attackers can bypass URL validation checks in Fission HTTPTriggers by using kubectl or direct API calls instead of the CLI, potentially violating security policies.","url":"https://insights.sbomify.com/CVE-2026-50569/"}