Fedora Account System
Red Hat Associate
Red Hat Customer
Disclaimer: Community trackers are created by Red Hat Product Security team on a best effort basis. Package maintainers are required to ascertain if the flaw indeed affects their package, before starting the update process. libgit2 versions v0.27.0 through v1.9.0 built with the libssh2 SSH backend (USE_SSH=libssh2) contain a shell command injection vulnerability that allows remote attackers to execute arbitrary commands on an SSH server by supplying a repository path containing unescaped shell metacharacters such as single quotes, semicolons, or pipes. The gen_proto() function in ssh_libssh2.c inserts the repository path directly into a shell command string without escaping special characters before passing it to libssh2_channel_exec(), enabling an attacker to craft a malicious submodule URL in a .gitmodules file that, when processed during a recursive clone, causes the remote server's shell to interpret injected commands under the victim's SSH user account.
We build with USE_SSH=no when %{rhel} is set (true for RHEL, CentOS Stream, EPEL and Fedora ELN), so this doesn't affect us on those platforms.
This is not correct, the bug *does* affect EPEL, it only does not affect ELN. The "if rhel" conditional you mention is only present *for ELN* because SSH support is unwanted there. But the epel10* and epel9 branches have SSH support enabled.
My apologies, I only checked the `libgit2` package (https://src.fedoraproject.org/rpms/libgit2/blob/epel10/f/libgit2.spec) and neglected to check the versioned ones.
Moved to libgit2_1.9, which has the SSH support enabled. The libgit2 package is still at v1.7 in EPEL, and has it disabled. Submitted updates for 1.9.7 to EPEL 10.3, 10.2, and EPEL 9.
FEDORA-EPEL-2026-da74b047d6 (libgit2_1.9-1.9.7-1.el10_3) has been submitted as an update to Fedora EPEL 10.3. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2026-da74b047d6
FEDORA-EPEL-2026-7671e4d4a3 (libgit2_1.9-1.9.7-1.el10_2) has been submitted as an update to Fedora EPEL 10.2. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2026-7671e4d4a3
FEDORA-EPEL-2026-a5f4b4222e (libgit2_1.9-1.9.7-1.el9) has been submitted as an update to Fedora EPEL 9. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2026-a5f4b4222e
FEDORA-EPEL-2026-da74b047d6 has been pushed to the Fedora EPEL 10.3 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2026-da74b047d6 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-EPEL-2026-a5f4b4222e has been pushed to the Fedora EPEL 9 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2026-a5f4b4222e See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-EPEL-2026-7671e4d4a3 has been pushed to the Fedora EPEL 10.2 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2026-7671e4d4a3 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-EPEL-2026-da74b047d6 (libgit2_1.9-1.9.7-1.el10_3) has been pushed to the Fedora EPEL 10.3 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-EPEL-2026-a5f4b4222e (libgit2_1.9-1.9.7-1.el9) has been pushed to the Fedora EPEL 9 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-EPEL-2026-7671e4d4a3 (libgit2_1.9-1.9.7-1.el10_2) has been pushed to the Fedora EPEL 10.2 stable repository. If problem still persists, please make note of it in this bug report.