Red Hat Gatekeeper 3.20.1 Fixes Two High-Severity Vulnerabilities
Quick Answer
The authority published RHSA-2026:74791 for Red Hat Gatekeeper 3.20. Red Hat published Gatekeeper v3.20.1 with the advisory-specific corrected packages or signed container-image digests for the listed CVEs. Affected deployments should be matched to the authority's exact scope and moved to the supported fixed release.
Confirm Scope And Apply The Supported Fix
What to do now: Inventory Red Hat Gatekeeper 3.20, match the exact affected release or feature, apply the authority-supported fixed build or service remediation, validate the dependent workflow, and preserve evidence.
Last verified: 2026-10-02 UTC. Recheck the authoritative advisory and supported distribution channel before changing production.
Scope And Authority
| Product scope | Red Hat Gatekeeper 3.20 |
|---|---|
| Advisory | RHSA-2026:74791 |
| CVEs | CVE-2026-32280, CVE-2026-32283 |
| Authoritative release date | 2026-10-01 22:38:04 UTC |
| Authority revision date | 2026-10-02 02:13:47 UTC |
| Affected versions | Gatekeeper 3.20 image builds before the v3.20.1 advisory digests. |
| Fixed version | Gatekeeper v3.20.1 advisory-listed signed image digests |
| CVSS base score | 7.5 (official CVSS v3.1) |
| CVSS severity | High |
| Exploitation status | Not stated by the authority; no exploitation claim is inferred. |
What Changed
Red Hat published Gatekeeper v3.20.1 with the advisory-specific corrected packages or signed container-image digests for the listed CVEs.
What To Validate Now
- Inventory. Locate Red Hat Gatekeeper 3.20 deployments, versions, enabled features, exposure paths, owners, and dependent services.
- Establish applicability. Match entitlement, product stream, architecture, source package or image repository, and each advisory's product status. Do not apply one branch's build or digest to another branch.
- Remediate. Use the supported Red Hat channel to deploy Gatekeeper v3.20.1 advisory-listed signed image digests. For containers, pin and verify the exact signed digest listed for the matching architecture and accelerator variant.
- Validate. Confirm the installed package build or running image digest, restart or redeploy affected workloads as required, validate application, cluster, accelerator, and recovery workflows, and record exceptions.
- 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
Confirm entitlement and branch support, test package or image compatibility, drain and redeploy clustered workloads deliberately, preserve prior digests and rollback evidence, and do not infer exploitation from severity.
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.

