Linux · openSUSE Leap · Security advisory · July 2, 2026

OPENSUSE-SU-2026:21213-1: containerd security update

OPENSUSE-SU-2026:21213-1, released July 2, 2026, fixes 10 CVEs in containerd (version 1.7.33-160000.1.1). None of them is reported as exploited. Patch Radar priority: Urgent.

Urgent
CVEs closed
10
1 rated Critical
Exploited
0
None reported
Highest CVSS
10.0
Base score, 0 to 10
Highest EPSS
0.0183
79th percentile

Priority of the 10 CVEs

Patch now 0 Urgent 1 High 7 Routine 2

Fixed package versions

ProductReleaseFixed in
containerdopensuse-leap 16.01.7.33-160000.1.1

CVEs this fix closes

PriorityCVETitleCVSSEPSSExploitation
Urgent CVE-2026-39821 Invoking failure to reject ASCII-only Punycode-encoded labels in golang.org/x/net/idna10.0 0.0183 None reported
High CVE-2026-33186 gRPC-Go has an authorization bypass via missing leading slash in :path9.1 0.0162 None reported
High CVE-2026-33814 Infinite loop in HTTP/2 transport when given bad SETTINGS_MAX_FRAME_SIZE in net/http/internal/http2 in golang.org/x/net7.5 0.0084 None reported
High CVE-2026-34986 osbuild-composer: A service for building customized OS artifacts, such as VM images and OSTree commits, that uses osbuild under the hood9.1 0.0066 None reported
High CVE-2026-35469 SpdyStream: DOS on CRI8.1 0.0066 None reported
High CVE-2026-53488 containerd: containerd is an open-source container runtime8.8 0.0018 None reported
High CVE-2024-25621 containerd affected by a local privilege escalation via wide permissions on CRI directory7.8 0.0017 None reported
High CVE-2026-46680 containerd: containerd is an open-source container runtime7.8 0.0016 None reported
Routine CVE-2026-47262 containerd: containerd is an open-source container runtime5.5 0.0027 None reported
Routine CVE-2025-64329 containerd CRI server: Host memory exhaustion through Attach goroutine leak5.5 0.0017 None reported
Showing 1 to 10 of 10 1

Patch Radar data is free to use with attribution. Terms and how to credit it.

Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.