Red Hat Goose Updates Address Four High-Severity Vulnerabilities

P1 — VALIDATE AND UPDATEHigh · 7.3 / 7.5 / 8.2 (CVSS v3.1)EXPLOITATION: NOT STATED

Quick Answer

Red Hat published RHSA-2026:80764 and RHSA-2026:80765 for Goose database migration tooling on RHEL 9.8 EUS and RHEL 10.2. Apply goose 1.45.0-1.el9_8 or 1.45.0-1.el10_2 for the matching branch only to the matching entitled branch, validate dependent services, and retain package and change evidence.

Confirm Scope And Apply The Supported Remediation

What to do now: Inventory Goose database migration tooling on RHEL 9.8 EUS and RHEL 10.2, compare installed NEVRAs with the exact advisory relationships, deploy goose 1.45.0-1.el9_8 or 1.45.0-1.el10_2 for the matching branch from the supported channel, restart dependent services where required, and validate representative operations.

Open the authoritative advisory

Last verified: 2026-10-12 UTC. Recheck the authoritative advisory and supported distribution channel before changing production.

Scope And Authority

Product scopeGoose database migration tooling on RHEL 9.8 EUS and RHEL 10.2
AdvisoryRHSA-2026:80764 / RHSA-2026:80765
CVEsCVE-2026-63127, CVE-2026-63128, CVE-2026-72718, CVE-2026-93599
Authoritative release date2026-10-12 13:06:45 UTC
Authority revision date2026-10-12 14:16:39 UTC
Affected versionsThe exact Goose package relationships for the entitled RHEL 9.8 EUS and RHEL 10.2 streams listed by RHSA-2026:80764 and RHSA-2026:80765.
Fixed versiongoose 1.45.0-1.el9_8 or 1.45.0-1.el10_2 for the matching branch
CVSS base score7.3 / 7.5 / 8.2 (CVSS v3.1)
CVSS severityHigh
Exploitation statusNot stated by the authority; no exploitation claim is inferred.

What Changed

Red Hat issued branch-specific Goose packages for four vulnerabilities affecting database migration workflows.

What To Validate Now

  1. Inventory. Locate Goose database migration tooling on RHEL 9.8 EUS and RHEL 10.2 deployments, versions, enabled features, exposure paths, owners, and dependent services.
  2. Establish applicability. Compare each deployment with the authority's affected-version statement: The exact Goose package relationships for the entitled RHEL 9.8 EUS and RHEL 10.2 streams listed by RHSA-2026:80764 and RHSA-2026:80765. Do not infer applicability from product family or severity alone.
  3. Remediate. Apply goose 1.45.0-1.el9_8 or 1.45.0-1.el10_2 for the matching branch through the supported vendor or project channel, following the current advisory and change-control requirements.
  4. Validate. Confirm the resulting version or managed-service state, exercise representative functionality and recovery paths, monitor for regressions, and document exceptions.
  5. 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

Do not substitute package builds across RHEL branches. Test Goose consumers, integrations, service restarts, and rollback before broad deployment. Preserve the authority snapshot, asset and owner records, before-and-after versions, change approval, installation output, validation results, exceptions, and rollback evidence.

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.