Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-50568 low CVSS 3.6

Vulnerability in github.com/fission/fission (CVE-2026-50568)

Summary

Vulnerability in github.com/fission/fission (CVE-2026-50568). Risk of unauthorized operations or information disclosure. Exploitable via SanitizeFilePath. Mitigation: upgrade to 1.25.0 or later.

Original description

The description as published by the source.

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.

Affected

  • Project: github.com/fission/fission
  • Versions: all versions through v1.24.0 with SanitizeFilePath in the tree
  • Audited commit: 647c141
  • Component: pkg/utils/utils.go:SanitizeFilePath
  • Callers: pkg/builder/builder.go:157,164,208, pkg/fetcher/fetcher.go:296,311,450,496,565,571
  • Configuration: default; requires a sibling directory to the safe dir to exist on the filesystem

Fix section (paste into the Fix / Patches field)

Fixed in v1.25.0 by:

  • PR #3445 (commit 8298e33e) — migrate every SanitizeFilePath call site (fetcher: storePath /…

Source: NIST National Vulnerability Database NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-50568 has been found in github.com/fission/fission.
Attackers can target a specific entry point like SanitizeFilePath over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 3.6/10.
What to do: upgrade github.com/fission/fission to 1.25.0 or later.
If unsure, ask your IT team or search "github.com/fission/fission CVE-2026-50568" on the vendor's site.

CVE-2026-50568 (github.com/fission/fission) — CWE-41 / CVSS v3 3.6
Attack vector: local / no user interaction
Attack surface: SanitizeFilePath / Clean / Fetch / Upload
Patched: 1.25.0 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-41) exists in github.com/fission/fission. Attackers reach the vulnerable code path via SanitizeFilePath.

📍 Affected scope

Check the vendor advisory for the affected versions of github.com/fission/fission. Attack surface: SanitizeFilePath / Clean / Fetch / Upload.

🔥 Severity

Severity: Low (CVSS 3.6/10). Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 1.25.0.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'github.com/fission/fission' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'github.com/fission/fission' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で github.com/fission/fission を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch 
    Upgrade github.com/fission/fission to 1.25.0

    ステージング環境で 1.25.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

go github.com/fission/fission
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"1.25.0"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details