Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-55108 high CVSS 8.5

Vulnerability in github.com/oam-dev/kubevela (CVE-2026-55108)

Summary

Vulnerability in github.com/oam-dev/kubevela (CVE-2026-55108). Risk of unauthorized operations or information disclosure. Exploitable via ComponentDefinition. Mitigation: upgrade to 1.11.0-alpha.4 or later.

Original description

The description as published by the source.

KubeVela Terraform remote loader DoS via unbounded file read in github.com/oam-dev/kubevela

Source: GitHub Security Advisories (Global) 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-55108 has been found in github.com/oam-dev/kubevela.
Attackers can target a specific entry point like ComponentDefinition over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 8.5/10.
What to do: upgrade github.com/oam-dev/kubevela to 1.11.0-alpha.4 or later.
If unsure, ask your IT team or search "github.com/oam-dev/kubevela CVE-2026-55108" on the vendor's site.

CVE-2026-55108 (github.com/oam-dev/kubevela) — CWE-59 / CVSS v3 8.5
Attack vector: remote (network-reachable) / no user interaction
Attack surface: ComponentDefinition / remote / variables.tf / os.ReadFile
Patched: 1.11.0-alpha.4 — 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-59) exists in github.com/oam-dev/kubevela. Attackers reach the vulnerable code path via ComponentDefinition.

📍 Affected scope

Check the vendor advisory for the affected versions of github.com/oam-dev/kubevela. Attack surface: ComponentDefinition / remote / variables.tf / os.ReadFile.

🔥 Severity

Severity: High (CVSS 8.5/10). Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 1.11.0-alpha.4.

🛡️ 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/oam-dev/kubevela' . 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/oam-dev/kubevela' . | grep -v node_modules

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

  2. 2
    Apply patch patch 
    Upgrade github.com/oam-dev/kubevela to 1.11.0-alpha.4

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

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

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

Affected packages

go github.com/oam-dev/kubevela
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"1.9.14"},{"introduced":"1.10.0-alpha.1"},{"fixed":"1.10.9"},{"introduced":"1.11.0-alpha.1"},{"fixed":"1.11.0-alpha.4"}]}]

References

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