Red Hat Updates OpenShift Mirror Registry to 2.0.13
Quick Answer
Deploy the supported 2.0.13 release for mirror registry for Red Hat OpenShift 2.0 and verify the fixed component image digests listed in RHSA-2026:100818.
Confirm Scope And Apply The Supported Remediation
What to do now: Record the installed product release, operator or installer version, architecture, running image digests and dependency owners. Match each component and architecture to the complete CSAF product and fixed-status records. A generic component CVSS value does not establish whether a vulnerable path is reachable. Apply prerequisite errata and the vendor-supported product update. Follow the installation and administration references linked in the advisory. Validate authentication, image push/pull and mirroring workflows, storage persistence and recovery. Retain registry version, image digests and representative transfer results.
Last verified: 2026-11-21 UTC. Recheck the authoritative advisory and supported distribution channel before changing production.
Scope And Authority
| Product scope | mirror registry for Red Hat OpenShift 2.0 |
|---|---|
| Advisory | RHSA-2026:100818 |
| CVEs | CVE-2026-110697, CVE-2026-123710, CVE-2026-33818, CVE-2026-56860, CVE-2026-56862 |
| Authoritative release date | 2026-11-20 20:47:16 UTC |
| Authority revision date | 2026-11-21T01:34:35+00:00 — CSAF current-release timestamp; generation alone is not treated as a separate material revision. |
| Affected versions | The mirror registry for Red Hat OpenShift 2.0 component images covered by RHSA-2026:100818 before deployment of its fixed images. The authority does not publish a universal affected-version range for the whole product. |
| Fixed version | mirror registry for Red Hat OpenShift 2.0 2.0.13 with the architecture-specific fixed image digests in RHSA-2026:100818. |
| CVSS base score | 9.9 (maximum component CVSS v3.1 published by Red Hat) |
| CVSS severity | Critical |
| Exploitation status | The cited authority does not state that these vulnerabilities are being exploited in the wild.; no exploitation claim is inferred. |
What Changed
Red Hat released mirror registry 2.0.13 with five component CVE fixes. Its CSAF identifies fixed registry images by architecture and digest; do not apply generic component scores as a deployment-specific risk rating.
What To Validate Now
- Inventory. Record the installed product release, operator or installer version, architecture, running image digests and dependency owners.
- Establish applicability. Match each component and architecture to the complete CSAF product and fixed-status records. A generic component CVSS value does not establish whether a vulnerable path is reachable.
- Remediate. Apply prerequisite errata and the vendor-supported product update. Follow the installation and administration references linked in the advisory.
- Validate. Validate authentication, image push/pull and mirroring workflows, storage persistence and recovery. Retain registry version, image digests and representative transfer results.
- 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
Plan workload and data recovery before the update. Red Hat marks the bulletin Critical, while its CVSS metrics describe underlying component vulnerabilities. Preserve the authoritative image matrix when documenting applicability.
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
- https://access.redhat.com/errata/RHSA-2026:100818
- https://security.access.redhat.com/data/csaf/v2/advisories/2026/rhsa-2026_100818.json
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.

