Skip to main content
HIGH

CVE-2022-23648

CVSS v3

7.5

HIGH

EPSS Score

27.4 %

exploit probability, as of 2026-10-19

CISA KEV

No

known exploited

Exploitation

—

SSVC status

Get an alert for each new CVE published for containerd/containerd.

Set up CVE WatchFree account · no credit card

Affected and fixed versions

Packages from OSV.dev and products from the vendors' CSAF advisories.

version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.

Packages

  • github.com/containerd/containerdGoall versions · fixed in 1.4.13

Vendor advisories

  • CVE-2022-23648 Red Hat Product Security3 known affected

    containerd: insecure handling of image volumes

    osp-director-provisioner-container as a component of Red Hat OpenStack Platform 16.2 · rhosp-rhel8-tech-preview/osp-director-operator as a component of Red Hat OpenStack Platform 16.2 · rhosp-rhel8/osp-director-downloader as a component of Red Hat OpenStack Platform 16.2

Full record on NVD

Description

containerd is a container runtime available as a daemon for Linux and Windows. A bug was found in containerd prior to versions 1.6.1, 1.5.10, and 1.14.12 where containers launched through containerd’s CRI implementation on Linux with a specially-crafted image configuration could gain access to read-only copies of arbitrary files and directories on the host. This may bypass any policy-based enforcement on container setup (including a Kubernetes Pod Security Policy) and expose potentially sensitive information. Kubernetes and crictl can both be configured to use containerd’s CRI implementation. This bug has been fixed in containerd 1.6.1, 1.5.10, and 1.4.12. Users should update to these versions to resolve the issue.

Technical details

Published
2022-03-03

Frequently asked questions

What is CVE-2022-23648?

containerd is a container runtime available as a daemon for Linux and Windows. A bug was found in containerd prior to versions 1.6.1, 1.5.10, and 1.14.12 where containers launched through containerd’s CRI implementation on Linux with a specially-crafted image configuration could gain access to read-only copies of arbitrary files and directories on the host. This may bypass any policy-based enforcement on container setup (including a Kubernetes Pod Security Policy) and expose potentially sensitive information. Kubernetes and crictl can both be configured to use containerd’s CRI implementation. This bug has been fixed in containerd 1.6.1, 1.5.10, and 1.4.12. Users should update to these versions to resolve the issue.

Is CVE-2022-23648 actively exploited?

Active exploitation of CVE-2022-23648 has not been confirmed. Its EPSS score was 27.4% on 2026-10-19, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2022-23648?

CVE-2022-23648 has a CVSS v3 base score of 7.5 (HIGH severity).

Running containerd/containerd? Hear about its next vulnerability

CVE Watch matches each new CVE to the vendors and products you list (vendor and product, not the version) and puts it in your alerts with its KEV and EPSS status.

Get alerts for this productCISA KEV additions, October 2026Search CVEs

Already have an account? Open CVE WatchNo credit card required · No monthly cap on website lookups · 250 API requests/month

Go further

Related vulnerabilities

Same product first, then the same vendor advisory and the same publication week.

Back to CVE Database