Red Hat Rust Updates Fix Git Repository Handling on RHEL 9

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

Quick Answer

Red Hat issued RHSA-2026:69097 for the RHEL 9.4 SAP E4S Rust toolchain and RHSA-2026:69109 for RHEL 9.6 EUS. Both address CVE-2026-53587 in libgit2: a malicious Git server can supply a crafted response that crashes an affected client. Install the package for the system's own support stream.

Confirm Scope And Apply The Supported Fix

What to do now: Inventory RHEL 9.4 SAP E4S and RHEL 9.6 EUS Rust toolchains, match the exact affected release or feature, apply the authority-supported fixed build or service remediation, validate the dependent workflow, and preserve evidence.

Open the authoritative advisory

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

Scope And Authority

Product scopeRHEL 9.4 SAP E4S and RHEL 9.6 EUS Rust toolchains
AdvisoryRHSA-2026:69097 / RHSA-2026:69109
CVECVE-2026-53587
Authoritative release date2026-09-21 05:09:56 UTC
Authority revision date2026-09-21 07:14:16 UTC
Affected versionsThe advisory-specific supported RHEL 9.4 SAP E4S and RHEL 9.6 EUS Rust toolchains builds before the listed fixed package or release.
Fixed versionrust 1.75.0-1.el9_4.1 / 1.84.1-1.el9_6.1
CVSS base score7.5 (CVSS v3.1)
CVSS severityHigh
Exploitation statusNot stated by the authority; no exploitation claim is inferred.

What Changed

The flaw is in libgit2's Git packet handling. A fixed-size comparison does not adequately check the received buffer length, so a malicious server's capability response can cause a heap out-of-bounds read and denial of service. This is a dependency used by the packaged toolchain, not a claim that Rust source code generally permits this attack.

What To Validate Now

  1. Inventory. Locate RHEL 9.4 SAP E4S and RHEL 9.6 EUS Rust toolchains deployments, versions, enabled features, exposure paths, owners, and dependent services.
  2. Establish applicability. Compare each deployment with the authority's affected-version statement: The advisory-specific supported RHEL 9.4 SAP E4S and RHEL 9.6 EUS Rust toolchains builds before the listed fixed package or release. Do not infer applicability from product family or severity alone.
  3. Remediate. Apply rust 1.75.0-1.el9_4.1 / 1.84.1-1.el9_6.1 through the supported vendor or project channel, following the current advisory and change-control requirements.
  4. Validate. Confirm the active Red Hat toolchain package in workstations and build images, then test approved repository-fetch and build workflows. Do not point production builds at a malicious server to validate the fix.
  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

Keep the branch mapping explicit: 1.75.0-1.el9_4.1 for RHEL 9.4 SAP E4S and 1.84.1-1.el9_6.1 for RHEL 9.6 EUS. Check the repository source and dependency workflow used by build jobs; the High score is not evidence that a malicious Git response was received.

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.