GHSA-XRGV-7VX6-5VX6
Git LFS may execute arbitrary commands via crafted Git configurations
Texto original en inglés · Ver en español
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N
Fuente: GitHub
Ciclo de vida de la vulnerabilidad
| Fecha | Fase | Evento | Detalle |
|---|---|---|---|
| Remediación | Parche v3.8.1 | github.com/git-lfs/git-lfs/v3 · -30 d desde divulgación | |
| Monitoreo | Detectada | Ingresó al índice | |
| Divulgación | Publicada | GHSA-XRGV-7VX6-5VX6 divulgada · CVSS 8.6 (GitHub) | |
| Divulgación | Modificada | Última actualización del registro | |
| Monitoreo | Fuente: GitHub Security Advisories | Registro visto por primera vez en GitHub Security Advisories | |
| Monitoreo | Fuente: OSV | Registro visto por primera vez en OSV | |
| Monitoreo | Verificada | Última verificación contra las fuentes |
Impact
When fetching objects from a malicious repository, Git LFS may execute an arbitrary command or binary after incorrectly parsing the Git configuration options defined for a submodule.
Git LFS reads Git configuration options without checking for embedded line-ending control characters. By inserting control characters such as line feed (LF) into certain values, an attacker may be able to mimic options that cause Git LFS to execute an arbitrary command when fetching or adding objects.
Git LFS has resolved this issue by always using an unambiguous format to read and parse Git configuration options.
Patches
This problem exists in all versions since 0.6.0 and is patched in v3.8.1. All users should upgrade to v3.8.1.
Workarounds
To work around the problem, users should prevent Git from initializing any submodules by disabling the `fetch.recurseSubmodules` and `submodule.recurse` configuration options and by never running the `git submodule init` command. Any submodules which have already been initialized in a repository may be deactivated with the `git submodule deinit` command.
For more information
If you have any questions or comments about this advisory:
* For general questions, start a discussion in the Git LFS discussion forum https://github.com/git-lfs/git-lfs/discussions.
* For reports of additional vulnerabilities, please follow the Git LFS security reporting policy https://github.com/git-lfs/git-lfs/blob/main/SECURITY.md.
Desglose de métricas
Rangos afectados
Estado del parche por paquete
| Paquete / producto | Estado | Corregida en | Desde divulgación | Última versión |
|---|---|---|---|---|
gogithub.com/git-lfs/git-lfs |
Sin parche | — | — | v2.5.2+incompatible afectada |
gogithub.com/git-lfs/git-lfs/v3 |
Corregida | v3.8.1 | -30 d | v3.8.1 no afectada |
3.8.1v3.8.1Arsenal público
Sin exploits, módulos ni PoC públicos conocidos a la fecha de verificación.
https://nvd.nist.gov/vuln/detail/CVE-2026-105802https://github.com/git-lfs/git-lfs/security/advisories/GHSA-xrgv-7vx6-5vx6https://github.com/git-lfs/git-lfs/commit/1b2672aaa29016e8004369df1406d2a73057f45fhttps://github.com/git-lfs/git-lfs/commit/39b73aa4db821fea6f0da8320128e5e1b919942dhttps://github.com/git-lfs/git-lfshttps://github.com/git-lfs/git-lfs/releases/tag/v3.8.1Las referencias externas se muestran para copiar: cve.llama.ec no lo redirige a otros sitios.
