CVE-2026-53489: containerd is an open-source container runtime

Routine

MEDIUM 6.5WATCHLISTUPGRADE

CVE-2026-53489 is a medium-severity flaw (CVSS 6.5) affecting containerd. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

containerd is an open-source container runtime. Versions prior to 2.3.2, 2.2.5 and 2.1.9 contain a bug where the CRI plugin restores container.log from a checkpoint image without validating a symlinked path. This could result in reading an arbitrary file on the host via kubectl logs. This issue has been fixed in versions 2.3.2, 2.2.5 and 2.1.9.

Why this priority

On your watchlist

A fixed release or distro patch exists.

Risk facts

CVSS score	6.5 (Medium)
Attack vector	Local
Attack complexity	Low
Privileges needed	Low
User interaction	None
EPSS exploit chance	0.2% (top 93%)
CISA exploited list	No
Weakness	CWE-61
Published	2026-07-01
Last modified	2026-07-02

Publisher (CNA): GitHub, Inc. · Vendor: linuxfoundation

Last updated 2026-07-02 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2026-07-01 19:16 UTCPublished CVE record published
2026-07-02 19:33 UTCUpdated Record last modified

linuxfoundation containerd UPGRADE

Affected: >= 2.1.0 and < 2.1.9 · >= 2.2.0 and < 2.2.5 · >= 2.3.0 and < 2.3.2

Fixed in: 2.1.9, 2.2.5, 2.3.2

Safe to downgrade to: a release before 2.1.0

1. Check installed version

apt-cache policy containerd || rpm -q containerd || containerd --version

2. UPGRADE to 2.1.9 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade containerd

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade containerd

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

3. If no update is available yet, DOWNGRADE to a release before 2.1.0 (Debian / Ubuntu)

apt-cache madison containerd sudo apt install containerd=<VERSION_BEFORE_2.1.0> sudo apt-mark hold containerd

3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list containerd sudo dnf downgrade containerd-<VERSION_BEFORE_2.1.0> sudo dnf versionlock add containerd

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Advisories and coverage

Official advisories

Google Cloud Security Bulletins: GCP-2026-051 2026-10-26

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-53489?

containerd: upgrade to 2.1.9, 2.2.5, 2.3.2. Exact commands for each OS are on this page.

Is CVE-2026-53489 being exploited?

CVE-2026-53489 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-53489 affect?

CVE-2026-53489 affects containerd. Severity is medium (CVSS 6.5). containerd is an open-source container runtime. Versions prior to 2.3.2, 2.2.5 and 2.1.9 contain a bug where the CRI plugin restores container.log from a checkpoint image without validating a symlinked path. This could result in reading an

How urgent is CVE-2026-53489?

Priority 29/100. On your watchlist

Software pages

containerd and runc vulnerabilities · Check Point vulnerabilities

Related CVEs

CVE-2026-53488 HIGH 8.8 UPGRADE containerd is an open-source container runtime
CVE-2026-46680 HIGH 7.8 UPGRADE containerd is an open-source container runtime
CVE-2026-50195 CRITICAL 9.9 UPGRADE containerd is an open-source container runtime
CVE-2026-47262 MEDIUM 5.5 UPGRADE containerd is an open-source container runtime
CVE-2026-53492 CRITICAL 9.6 UPGRADE containerd is an open-source container runtime

References

← Back to latest CVEs