Git is a fast, scalable, distributed revision control system with an unusually rich command set that provides both high-level operations and full access to internals. When cloning a repository Git knows to optionally fetch a bundle advertised by the remote server, which allows the server-side to offload parts of the clone to a CDN. The Git client does not perform sufficient validation of the advertised bundles, which allows the remote side to perform protocol injection. This protocol injection can cause the client to write the fetched bundle to a location controlled by the adversary. The fetched content is fully controlled by the server, which can in the worst case lead to arbitrary code execution. The use of bundle URIs is not enabled by default and can be controlled by the bundle.heuristic config option. Some cases of the vulnerability require that the adversary is in control of where a repository will be cloned to. This either requires social engineering or a recursive clone with submodules. These cases can thus be avoided by disabling recursive clones. This vulnerability is fixed in v2.43.7, v2.44.4, v2.45.4, v2.46.4, v2.47.3, v2.48.2, v2.49.1, and v2.50.1.
This issue has been addressed in the following products: Red Hat Enterprise Linux 9 Via RHSA-2025:11462 https://access.redhat.com/errata/RHSA-2025:11462
This issue has been addressed in the following products: Red Hat Enterprise Linux 10 Via RHSA-2025:11533 https://access.redhat.com/errata/RHSA-2025:11533
This issue has been addressed in the following products: Red Hat Enterprise Linux 8 Via RHSA-2025:11534 https://access.redhat.com/errata/RHSA-2025:11534
This issue has been addressed in the following products: Red Hat Enterprise Linux 9.4 Extended Update Support Via RHSA-2025:11686 https://access.redhat.com/errata/RHSA-2025:11686
This issue has been addressed in the following products: Red Hat Enterprise Linux 9.2 Update Services for SAP Solutions Via RHSA-2025:11795 https://access.redhat.com/errata/RHSA-2025:11795
This issue has been addressed in the following products: Red Hat Enterprise Linux 8.8 Update Services for SAP Solutions Red Hat Enterprise Linux 8.8 Telecommunications Update Service Via RHSA-2025:11794 https://access.redhat.com/errata/RHSA-2025:11794
This issue has been addressed in the following products: RHEL-8 based Middleware Containers Via RHSA-2025:13276 https://access.redhat.com/errata/RHSA-2025:13276
This issue has been addressed in the following products: Red Hat OpenShift Container Platform 4.18 Via RHSA-2025:13325 https://access.redhat.com/errata/RHSA-2025:13325
This issue has been addressed in the following products: Red Hat OpenShift Container Platform 4.19 Via RHSA-2025:13933 https://access.redhat.com/errata/RHSA-2025:13933
This issue has been addressed in the following products: Red Hat OpenShift Container Platform 4.17 Via RHSA-2025:14059 https://access.redhat.com/errata/RHSA-2025:14059
This issue has been addressed in the following products: Red Hat OpenShift Container Platform 4.15 Via RHSA-2025:14396 https://access.redhat.com/errata/RHSA-2025:14396
This issue has been addressed in the following products: Red Hat OpenShift Container Platform 4.14 Via RHSA-2025:14853 https://access.redhat.com/errata/RHSA-2025:14853
This issue has been addressed in the following products: Red Hat OpenShift Container Platform 4.16 Via RHSA-2025:14858 https://access.redhat.com/errata/RHSA-2025:14858
This issue has been addressed in the following products: Red Hat Web Terminal 1.12 on RHEL 9 Via RHSA-2025:15827 https://access.redhat.com/errata/RHSA-2025:15827
This issue has been addressed in the following products: Red Hat Web Terminal 1.11 on RHEL 9 Via RHSA-2025:15828 https://access.redhat.com/errata/RHSA-2025:15828
This issue has been addressed in the following products: Red Hat OpenShift Container Platform 4.13 Via RHSA-2025:15672 https://access.redhat.com/errata/RHSA-2025:15672