Categories
CVE-2026-50567 high CVSS 7.7

Path Traversal in github.com/fission/fission (CVE-2026-50567)

Summary

Path traversal in github.com/fission/fission (CVE-2026-50567). Data can be tampered with by attackers. Exploitable via Unarchive. Mitigation: upgrade to 1.25.0 or later.

Original description

The description as published by the source.

Unarchive in pkg/utils/zip.go joined each archive entry name with the destination directory via filepath.Join and wrote the result without checking whether the resolved path stayed under the destination. A zip entry named
../../tmp/evil therefore landed at /tmp/evil. An attacker who could control a Package.Spec.Source.URL or Deployment.URL archive could induce the fetcher (running as the per-environment pod's fission-fetcher sidecar) to write
files anywhere that process could reach: into other tenants' /packages// directories, into mounted secret/config volumes, or into the fetcher's own binary.

Affected

  • Project: github.com/fission/fission
  • Versions: all up to and including v1.24.0
  • Audited commit: 647c141
  • Component: pkg/utils/zip.go (Unarchive)
  • Configuration: default; triggered when the fetcher downloads and extracts a zip archive

Fix section (paste into the Fix / Patches field)

Fixed in v1.25.0 by:

  • PR #3444 (commit 55704aca) — Unarchive now opens an os.Root on the destination, validates each
    archive entry name (rejects absolute paths and .. traversal), and refuses symlink entries up front. The os.Root confines every mkdir / create to the destination in the kernel.

Regression coverage: `TestUnarchiveZ…

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-50567 has been found in github.com/fission/fission.
Attackers can target a specific entry point like Unarchive over the network to misuse the product.
Data can be tampered with by attackers. CVSS score: 7.7/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-50567" on the vendor's site.

CVE-2026-50567 (github.com/fission/fission) — CWE-22 / CVSS v3 7.7
Attack vector: remote (network-reachable) / no user interaction
Attack surface: Unarchive / filepath.Join / Package.Spec.Source.URL / Deployment.URL
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

Path traversal (CWE-22) exists in github.com/fission/fission. Attackers reach the vulnerable code path via Unarchive.

📍 Affected scope

Check the vendor advisory for the affected versions of github.com/fission/fission. Attack surface: Unarchive / filepath.Join / Package.Spec.Source.URL / Deployment.URL.

🔥 Severity

Severity: High (CVSS 7.7/10). Data can be tampered with by attackers.

🔧 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