CVE-2022-23648: Insecure handling of image volumes in github.com/containerd/containerd

Summary

21/08/2024
Yes i
High
7.5

CVE-2022-23648: containerd CRI plugin: Insecure handling of image volumes in github.com/containerd/containerd. Affects github.com/containerd/containerd across 3 version ranges.

< 1.4.13 >= 1.5.0, < 1.5.10 >= 1.6.0, < 1.6.1

Fixed in 1.4.13, 1.5.10 or 1.6.1, depending on the release line you run. How to fix ↓

Also tracked for

The same CVE-2022-23648 is tracked separately for each ecosystem and vendor. Its fix information is the same; the package and affected versions differ.

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Sponsored MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

github.com/containerd/containerd is a Go package that provides a container runtime for Linux. It is widely used in container orchestration systems and provides functionality for managing containers, images, and volumes. This vulnerability affects versions 0.x, 1.4.13, 1.5.0 - 1.5.10, and 1.6.0 - 1.6.1 of the package.

Vulnerability Detail

The containerd CRI plugin in github.com/containerd/containerd has an insecure handling of image volumes. This vulnerability could allow an attacker to manipulate or access sensitive data within container volumes, potentially leading to unauthorized access or data leakage. The issue originates from a flaw in the handling of image volumes, which can be exploited by an attacker with access to the container runtime environment.

How To Fix

Latest published version: v1.7.36 as of 22 Oct 2026

go get github.com/containerd/containerd@v1.7.36

Upgrading to it may include breaking changes; the versions below are the minimum fixed release for this vulnerability.

If you can't move to the latest

The minimum fixed version depends on the release line you run.

  • < 1.4.13 1.4.13
    go get github.com/containerd/containerd@v1.4.13
  • >= 1.5.0, < 1.5.10 1.5.10
    go get github.com/containerd/containerd@v1.5.10
  • >= 1.6.0, < 1.6.1 1.6.1
    go get github.com/containerd/containerd@v1.6.1

Tip — Not sure which release line you're on? Vulert can find the fix for the version you are using. Scan free →

Workaround

There is no known workaround for this vulnerability. It is essential to update the package to the fixed versions mentioned above.

Conclusion

The insecure handling of image volumes in github.com/containerd/containerd can lead to unauthorized access or data leakage within container volumes. It is crucial to update the package to the fixed versions mentioned in the 'how_to_fix' section to mitigate this vulnerability.

See every vulnerability recorded for github.com/containerd/containerd →

Share this vulnerability

FAQ

This vulnerability could allow an attacker to manipulate or access sensitive data within container volumes, potentially leading to unauthorized access or data leakage.

You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability. Simply upload your Gopkg.lock file, and Vulert will analyze it in real-time.

No, only versions 0.x, 1.4.13, 1.5.0 - 1.5.10, and 1.6.0 - 1.6.1 are affected. It is recommended to update to the fixed versions mentioned in the 'how_to_fix' section.

No, there is no known workaround. It is crucial to update the package to the fixed versions.

No, this vulnerability requires an attacker to have access to the container runtime environment.

Related vulnerabilities

Recent vulnerabilities recorded for github.com/containerd/containerd.

How To Fix

Latest published version: v1.7.36 as of 22 Oct 2026

go get github.com/containerd/containerd@v1.7.36

Upgrading to it may include breaking changes; the versions below are the minimum fixed release for this vulnerability.

If you can't move to the latest

The minimum fixed version depends on the release line you run.

  • < 1.4.13 1.4.13
    go get github.com/containerd/containerd@v1.4.13
  • >= 1.5.0, < 1.5.10 1.5.10
    go get github.com/containerd/containerd@v1.5.10
  • >= 1.6.0, < 1.6.1 1.6.1
    go get github.com/containerd/containerd@v1.6.1

Tip — Not sure which release line you're on? Vulert can find the fix for the version you are using. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback