containernetworking/cni improper limitation of path name

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

7.2 · CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H

EPSS

• CVE-2021-20206: 1.52% estimated exploitation activity in the next 30 days; percentile 74.69 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

An improper limitation of path name flaw was found in containernetworking/cni in versions before 0.8.1. When specifying the plugin to load in the 'type' field in the network configuration, it is possible to use special elements such as "../" separators to reference binaries elsewhere on the system. This flaw allows an attacker to execute other existing binaries other than the cni plugins/types, such as 'reboot'. The highest threat from this vulnerability is to confidentiality, integrity, as well as system availability. Specific Go Packages Affected github.com/containernetworking/cni/pkg/invoke

Published by the source

15 Feb 2022, 01:57 UTC

Last modified by the source

2 Oct 2023, 13:12 UTC

Source last checked

26 Oct 2026, 14:59 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-xjqr-g762-pxwp

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2021-20206

Advisory: containernetworking/cni improper limitation of path name
IDs: CVE-2021-20206, GHSA-xjqr-g762-pxwp
Record: https://patchnext.com/advisories/cve-2021-20206 (revision 1, source checked 26 Oct 2026, 14:59 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.2)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/containernetworking/cni 0.8.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/containernetworking/cni: affected < 0.8.1; fixed in 0.8.1

## Suggested inspection (read-only)
- Go github.com/containernetworking/cni: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/containernetworking/cni.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-xjqr-g762-pxwp (GitHub-reviewed advisory GHSA-xjqr-g762-pxwp lists affected ranges: Go github.com/containernetworking/cni >=0 <0.8.1)

Commands are suggestions: review each one before running it.