CVE-2026-7374 - KubeVirt has a Link Following vulnerability

CVE-2026-7374 + KubeVirt has a Link Following vulnerability + Critical + 2026-05-26

One-sentence business risk

Broken authentication or authorization can expose tenant data and administrator actions, which buyers treat as a release blocker.

Research notes

  • Root cause: A flaw was found in KubeVirt’s virt-handler component.
  • Affected versions: go:kubevirt.io/kubevirt >= 1.8.0-alpha.0, < 1.8.3; go:kubevirt.io/kubevirt >= 1.7.0-alpha.0, < 1.7.4; go:kubevirt.io/kubevirt < 1.6.6.
  • Fixed / safe versions: 1.6.6, 1.7.4, 1.8.3.
  • Public exploit / PoC signal: the consulted NVD/GHSA/vendor sources describe the trigger class; treat it as reproducible until patched.
  • CVSS: use upstream advisory score .

Exact vulnerable code pattern

target = join(base_dir, user_path); read_or_write(target)

Fixed / mitigated code pattern

target = realpath(join(base_dir, user_path)); assert target is inside realpath(base_dir)

Dependency or runtime update:

go list -m all | grep -i kubevirt || true
go get kubevirt.io/kubevirt@latest
go mod tidy
go test ./...

Step-by-step integration guide

  1. Inventory kubevirt.io/kubevirt across source, lockfiles, SBOMs, container images, CI images, and deployment manifests.
  2. Upgrade to 1.6.6, 1.7.4, 1.8.3 or apply the exact vendor patch referenced below.
  3. Replace the vulnerable path-traversal pattern with the fixed pattern and fail closed on malformed input.
  4. Add a regression test that exercises the advisory trigger and proves the request is rejected, bounded, or authorized.
  5. Deploy through canary, monitor security logs and resource metrics, then remove temporary edge blocks only after all runtimes are fixed.

Alternative mitigations

  • Disable the vulnerable feature path while the package/runtime update rolls out.
  • Add WAF or reverse-proxy rules for traversal tokens, prototype-polluting keys, oversized frames, shell metacharacters, or unauthenticated tool calls matching the trigger class.
  • Restrict internal egress, rotate exposed secrets, and revoke affected tokens/keys if the vulnerability can disclose config, logs, JWT secrets, proxy credentials, or PKI material.
  • For admin/API authorization issues, temporarily require elevated roles and explicit ownership checks at the gateway.

Detection signature

id: cve-2026-7374-kubevirt-has-a-link-following-vulnerability
source: GitHub Advisory Database
dependency_or_product: "kubevirt.io/kubevirt"
affected: "go:kubevirt.io/kubevirt >= 1.8.0-alpha.0, < 1.8.3; go:kubevirt.io/kubevirt >= 1.7.0-alpha.0, < 1.7.4; go:kubevirt.io/kubevirt < 1.6.6"
fixed: "1.6.6, 1.7.4, 1.8.3"
signals:
  - "path-traversal"
  - "../"
  - "__proto__"
  - "tools/call"
  - "wp_ajax_nopriv"
  - "pickle.loads"
  - "shell command construction"
action: "upgrade, add regression test, and verify deploy artifact"

Copy-paste skill

You are remediating CVE-2026-7374 (KubeVirt has a Link Following vulnerability) in this repository.

Find every affected dependency, runtime, image, service configuration, and reachable code path. Upgrade or patch to 1.6.6, 1.7.4, 1.8.3. Replace the vulnerable path-traversal pattern with a fail-closed implementation, add a regression test for the trigger shape, and update deployment/SBOM artifacts. If this repository does not control the affected runtime, create TRIAGE.md naming the owner, affected version, fixed version, and blocking decision.

Keywords, affected tech stack, and revenue tags

  • Keywords: CVE-2026-7374, path-traversal, kubevirt.io/kubevirt, GitHub Advisory Database.
  • Affected tech stack: go.
  • Revenue tags: sellable_to_fintech, enterprise_blocker, zero_day_gold.

References