Red Hat CNI Plugins Update Addresses Five RHEL 9 Flaws
Tech GuruQuick Answer
RHSA-2026:70391 updates the RHEL 9.8 EUS containernetworking-plugins package for five Go-library security issues. Red Hat lists 1:1.9.0-4.el9_8, including RPM epoch 1, as the fixed package. Match the entitled repository and plugin binaries used on each host; changing a separate Go compiler installation is not evidence that this packaged binary has been updated.
Confirm Scope And Apply The Supported Fix
What to do now: Inventory RHEL 9.8 EUS containernetworking-plugins packages, match the exact affected release or feature, apply the authority-supported fixed build or service remediation, validate the dependent workflow, and preserve evidence.
Source recheck: October 2, 2026 UTC, against Red Hat's structured CSAF advisory. The dates above distinguish initial issue from current CSAF generation. Confirm repository entitlement and installed/running package state locally before closing the change.
Scope And Authority
| Product scope | RHEL 9.8 EUS containernetworking-plugins packages |
|---|---|
| Advisory | RHSA-2026:70391 |
| CVEs | CVE-2026-33818, CVE-2026-56853, CVE-2026-56858, CVE-2026-56860, CVE-2026-56862 |
| Authoritative release date | RHSA-2026:70391: 2026-09-23T03:17:50+00:00 |
| Authority revision date | RHSA-2026:70391: 2026-10-02T18:48:26+00:00 (CSAF current generation) |
| Affected versions | The exact entitled RHEL 9.8 EUS containernetworking-plugins packages builds before the branch-specific packages listed by Red Hat |
| Fixed version | containernetworking-plugins 1:1.9.0-4.el9_8 (RPM epoch 1), or the supported superseding build for the same entitled stream and architecture. |
| CVSS base score | 7.5 / 8.1 (CVSS v3.1) |
| CVSS severity | High |
| Exploitation status | Not stated by the authority; no exploitation claim is inferred. |
What Changed
The bundled-library fixes concern ASN.1 recursion, URL path-resolution cost, unencrypted HTTP/2 connection handling, HTML template escaping and TLS KeyUpdate processing. Their inclusion in the package advisory does not mean every host exposes all of those functions. Use the Red Hat package decision and actual runtime paths together, rather than inferring a remotely exploitable CNI service from the highest score.
What To Validate Now
- Inventory. Record RHEL/EUS entitlement, architecture, package epoch/version/release, container runtime and the plugin paths it actually invokes. Check every node and distinguish vendor-managed copies from separately installed binaries.
- Establish applicability. Compare each deployment with the authority's affected-version statement: The exact entitled RHEL 9.8 EUS containernetworking-plugins packages builds before the branch-specific packages listed by Red Hat Do not infer applicability from product family or severity alone.
- Remediate. Apply containernetworking-plugins 1.9.0-4.el9_8 through the supported vendor or project channel, following the current advisory and change-control requirements.
- Validate. On an approved staging node, create and remove disposable containers through the normal runtime and verify address allocation, connectivity and cleanup. Confirm the runtime uses the updated plugin path; do not manually remove production interfaces or firewall rules to test the update.
- Retain evidence. Preserve asset and owner identifiers, the applicability decision, before-and-after versions, change approval, installation output, validation results, and any exception or rollback record.
Operational Cautions
Use the exact supported release stream and repository. Test dependencies, clusters, integrations, and rollback before broad deployment; a CVSS rating or reachable feature is not evidence of exploitation.
Evidence To Retain
- Exact product, release stream, package or application version, enabled feature, environment, and accountable owner.
- UTC timestamps, authority revision, approved change record, installer or package-manager output, and resulting version.
- Relevant logs and monitoring evidence, test results, exceptions, compensating controls, and rollback decisions.
Related TechGeeks Resources
Authoritative References
Correction policy: If the authority changes affected versions, fixed versions, severity, exploitation information, mitigations, or required action, TechGeeks will update this notice and its verification date.
