Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-41326 high CVSS 8.2

Vulnerability in github.com/kata-containers/kata-containers (CVE-2026-41326)

Summary

Vulnerability in github.com/kata-containers/kata-containers (CVE-2026-41326). Confidential information can be exposed externally. Exploitable via policy_data.common.cpath. Mitigation: upgrade to 0.0.0-20260422180503-1b9e49eb2763 or later.

Original description

The description as published by the source.

Summary

An oversight in the CopyFile policy (and perhaps the CopyFile handler) allows untrusted hosts to write to arbitrary locations inside the guest workload image. This can be used to overwrite binaries inside the guest and exfiltrate data from containers; even those running inside CVMs.

Details

Here is the policy that covers CopyFile requests.

CopyFileRequest if {
    print("CopyFileRequest: input.path =", input.path)
        
    check_directory_traversal(input.path)
        
    some regex1 in policy_data.request_defaults.CopyFileRequest
    regex2 := replace(regex1, "$(sfprefix)", policy_data.common.sfprefix)
    regex3 := replace(regex2, "$(cpath)", policy_data.common.cpath)
    regex4 := replace(regex3, "$(bundle-id)", "[a-z0-9]{64}")
    print("CopyFileRequest: regex4 =", regex4)
    
    regex.match(regex4, input.path)
      
    print("CopyFileRequest: true")
}

This checks that files are being copied to policy_data.common.cpath, which is typically set to /run/kata-containers/shared/containers. In other words, you're allowed to copy files to anywhere inside the shared dir.

For reference, here is the CopyFile message. Note that none of the other fields are check in the policy.

message CopyFileRequest {
	// Path is the destination file in the guest. It must be absolute,
	// canonical and below /run.
	string path = 1;
	// FileSize is the expected file size, for security reasons write operations
	// are made in a temporary file, once it has th…

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-41326 has been found in github.com/kata-containers/kata-containers.
Attackers can target a specific entry point like policy_data.common.cpath over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 8.2/10.
What to do: upgrade github.com/kata-containers/kata-containers to 0.0.0-20260422180503-1b9e49eb2763 or later.
If unsure, ask your IT team or search "github.com/kata-containers/kata-containers CVE-2026-41326" on the vendor's site.

CVE-2026-41326 (github.com/kata-containers/kata-containers) — CWE-61 / CVSS v3 8.2
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: policy_data.common.cpath / path / data / genpolicy
Patched: 0.0.0-20260422180503-1b9e49eb2763 — 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-61) exists in github.com/kata-containers/kata-containers. Attackers reach the vulnerable code path via policy_data.common.cpath without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of github.com/kata-containers/kata-containers. Attack surface: policy_data.common.cpath / path / data / genpolicy.

🔥 Severity

Severity: High (CVSS 8.2/10). Confidential information can be exposed externally.

🔧 How to fix

Update to 0.0.0-20260422180503-1b9e49eb2763.

🛡️ 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/kata-containers/kata-containers' . 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/kata-containers/kata-containers' . | grep -v node_modules

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

  2. 2
    Apply patch patch 
    Upgrade github.com/kata-containers/kata-containers to 0.0.0-20260422180503-1b9e49eb2763

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

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

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

Affected packages

go github.com/kata-containers/kata-containers
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"0.0.0-20260422180503-1b9e49eb2763"}]}]

References

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