USN-8472-1: containerd vulnerabilities

Published Jun 25, 2026
·
Updated

It was discovered that containerd incorrectly handled HTTP/2 SETTINGS frames. A remote attacker could possibly use this issue to cause containerd to enter an infinite loop, resulting in a denial of service. (CVE-2026-33814) Jakub Ciolek and Kyle Elliott discovered that containerd incorrectly handled group parsing when creating containers from images. An attacker could possibly use this issue to cause containerd to consume excessive memory, resulting in a denial of service. (CVE-2026-47262) Henry Beberman and Robert Prast discovered that containerd incorrectly validated image references when importing container checkpoints. An attacker could possibly use this issue to poison the local image cache and execute arbitrary code in other pods. This issue only affected Ubuntu 22.04 LTS, Ubuntu 24.04 LTS, Ubuntu 25.10 and Ubuntu 26.04 LTS. (CVE-2026-50195) Robert Prast discovered that containerd incorrectly propagated labels from image configurations to containers. An attacker could possibly use this issue to execute arbitrary code on the host. (CVE-2026-53488) Yuming Zhang, Song Li, Sangwon Ryu, Henry Beberman, Robert Prast, Kyle Elliott and Zhenchen Wang discovered that containerd incorrectly validated symlinked paths when restoring container checkpoints. An attacker could possibly use this issue to read arbitrary files on the host, resulting in information disclosure. This issue only affected Ubuntu 22.04 LTS, Ubuntu 24.04 LTS, Ubuntu 25.10 and Ubuntu 26.04 LTS. (CVE-2026-53489) Robert Prast discovered that containerd incorrectly trusted device interface annotations when restoring container checkpoints. An attacker could possibly use this issue to bypass resource allocation restrictions and inject devices or host mounts into a container. This issue only affected Ubuntu 22.04 LTS, Ubuntu 24.04 LTS, Ubuntu 25.10 and Ubuntu 26.04 LTS. (CVE-2026-53492)

Affected Software

11 affected componentsFixes available
containerd
All of the following
ubuntu/containerd<2.2.2-0ubuntu1.1
2.2.2-0ubuntu1.1
Ubuntu Ubuntu=26.04
All of the following
ubuntu/containerd<2.2.1-0ubuntu1~25.10.2
2.2.1-0ubuntu1~25.10.2
Ubuntu Ubuntu=25.10
All of the following
ubuntu/containerd<2.2.1-0ubuntu1~24.04.3
2.2.1-0ubuntu1~24.04.3
Ubuntu Ubuntu=24.04
All of the following
ubuntu/containerd<2.2.1-0ubuntu1~22.04.2
2.2.1-0ubuntu1~22.04.2
Ubuntu Ubuntu=22.04
All of the following
ubuntu/containerd<Ubuntu Pro
Ubuntu Pro
Ubuntu Ubuntu=20.04

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade ubuntu/containerd to a version that resolves this vulnerability.

    Fixed in 2.2.2-0ubuntu1.1
  2. Upgrade

    Upgrade ubuntu/containerd to a version that resolves this vulnerability.

    Fixed in 2.2.1-0ubuntu1~25.10.2
  3. Upgrade

    Upgrade ubuntu/containerd to a version that resolves this vulnerability.

    Fixed in 2.2.1-0ubuntu1~24.04.3
  4. Upgrade

    Upgrade ubuntu/containerd to a version that resolves this vulnerability.

    Fixed in 2.2.1-0ubuntu1~22.04.2
  5. Upgrade

    Upgrade ubuntu/containerd to a version that resolves this vulnerability.

    Fixed in Ubuntu Pro
  6. Upgrade

    Upgrade containerd to a version that resolves this vulnerability.

    Patch USN-8472-1

Event History

Jun 25, 2026
Advisory Published
via Ubuntu·12:00 AM
Data Sourced
via Ubuntu·12:00 AM
DescriptionAffected Software

Child vulnerabilities

Contains the following vulnerabilities.

Frequently Asked Questions

1

What are the specific vulnerabilities associated with USN-8472-1?

USN-8472-1 addresses multiple vulnerabilities in containerd, specifically CVE-2026-53492, CVE-2026-53489, and CVE-2026-53488.

2

What is the risk level of USN-8472-1?

The risk level of USN-8472-1 is assessed at 55, indicating significant potential impact.

3

How do I mitigate the vulnerabilities outlined in USN-8472-1?

To mitigate the vulnerabilities in USN-8472-1, users should apply the latest security updates for containerd as soon as they are available.

4

Are there any known exploits for the vulnerabilities in USN-8472-1?

As of now, there are no widespread known exploits specifically targeting the vulnerabilities outlined in USN-8472-1.

5

Who is affected by the vulnerabilities covered in USN-8472-1?

Any user or organization utilizing vulnerable versions of containerd is potentially affected by the vulnerabilities covered in USN-8472-1.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203