Summary
The Container Network Interface (CNI) project consists of a specification and libraries for writing plug-ins for configuring network interfaces in Linux containers, along with a number of supported plug-ins. CNI concerns itself only with network connectivity of containers and removing allocated resources when the container is deleted.
Security Fix(es):
* net: golang: Go net package: Denial of Service via long CNAME response in LookupCNAME (CVE-2026-33811)
* crypto/x509: golang: golang crypto/x509: Denial of Service via excessive processing of DNS SAN entries (CVE-2026-27145)
Bug Fix(es) and Enhancement(s):
* containernetworking-plugins - update to the latest upstream release (JIRA:Rocky Linux-212439)
For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.
Additional Changes:
For detailed information on changes in this release, see the Rocky Linux 9 Release Notes linked from the References section.
Fixed packages 12
| Release | Package | Fixed in |
|---|---|---|
| Rocky Linux · 9 | containernetworking-plugins | 1:1.9.1-2.el9 |
| Rocky Linux · 9 | containernetworking-plugins | 1:1.9.1-2.el9 |
| Rocky Linux · 9 | containernetworking-plugins | 1:1.9.1-2.el9 |
| Rocky Linux · 9 | containernetworking-plugins | 1:1.9.1-2.el9 |
| Rocky Linux · 9 | containernetworking-plugins-debuginfo | 1:1.9.1-2.el9 |
| Rocky Linux · 9 | containernetworking-plugins-debuginfo | 1:1.9.1-2.el9 |
| Rocky Linux · 9 | containernetworking-plugins-debuginfo | 1:1.9.1-2.el9 |
| Rocky Linux · 9 | containernetworking-plugins-debuginfo | 1:1.9.1-2.el9 |
| Rocky Linux · 9 | containernetworking-plugins-debugsource | 1:1.9.1-2.el9 |
| Rocky Linux · 9 | containernetworking-plugins-debugsource | 1:1.9.1-2.el9 |
| Rocky Linux · 9 | containernetworking-plugins-debugsource | 1:1.9.1-2.el9 |
| Rocky Linux · 9 | containernetworking-plugins-debugsource | 1:1.9.1-2.el9 |
Vulnerabilities 2
-
High 7.5
Crash when handling long CNAME response in net
When using LookupCNAME with the cgo DNS resolver, a very long CNAME response can trigger a double-free of C memory and a crash.
-
Medium 6.5CVE-2026-27145 Public exploit
Inefficient candidate hostname parsing in crypto/x509
(*x509.Certificate).VerifyHostname previously called matchHostnames in a loop over all DNS Subject Alternative Name (SAN) entries. This caused strings.Split(host, ".") to execute repeatedly on the same input hostname. With a large DNS SAN list, verification c…