CVE REMEDIATION GUIDE
Review reviewHighFixed-version data available

CVE-2026-28406 remediation guide

chainguard-forks kaniko, OpenShift Serverless

kaniko is a tool to build container images from a Dockerfile, inside a container or Kubernetes cluster. Starting in version 1.25.4 and prior to version 1.25.10, kaniko unpacks build context archives using `filepath.Join(dest, cleanedName)` without enforcing that the final path stays within `dest`. A tar entry like `../outside.txt` escapes the extraction root and writes files outside the destination directory. In environments with registry authentication, this can be chained with docker credential helpers to achieve code execution within the executor process. Version 1.25.10 uses securejoin...

Open CVE record
Productchainguard-forks kaniko, OpenShift Serverless
Affected versions>= >= 1.25.4, < 1.25.10, >= 1.25.4 < 1.25.10
Fixed versions1.25.10
Priority basisReview · CVSS 8.2 · EPSS 0.61%
01

Identify the affected asset

Confirm whether chainguard-forks kaniko, OpenShift Serverless is installed, record the deployed version and installation path, and identify exposed interfaces.

  • Record the product name, package or appliance identifier, and installed version.
  • Identify internet-facing, administrative, API, and internal access paths.
  • Preserve the pre-change configuration and relevant service logs.
02

Validate the affected-version match

Compare the deployed version with the affected range: >= >= 1.25.4, < 1.25.10, >= 1.25.4 < 1.25.10. Treat incomplete inventory results as unresolved.

03

Prioritize with independent signals

The CVSS severity warrants an early asset and exposure review. Combine this signal with asset criticality, exposure, compensating controls, and business impact.

04

Apply supported remediation

Follow the vendor advisory or supported update path. Current fixed-version status: 1.25.10. Preserve configuration and rollback material before change.

05

Verify the result

Confirm the resulting version, service health, authentication and access paths, monitoring coverage, and relevant security logs.

  • Confirm the expected version and package state.
  • Run a functional health check for critical service paths.
  • Review authentication, error, application, and security monitoring logs.
  • Reassess exposure if the supported fix cannot be applied.

Operational boundary

This page does not replace the vendor advisory, support contract, change-management process, or recovery plan. Do not infer that an asset is unaffected from an incomplete inventory query or a missing fixed-version field.

CVE-2026-28406 Remediation Guide | SECUFOCUS NOW