Approved changes feed: RSS · Atom
cpe:2.3:a:git:git:*:*:*:*:*:*:*:*
part: a version: * update: *
| Vendor | Git (6ebdb489-ead0-5dd4-8271-23d1b43b29e9) |
|---|---|
| Product | Git (a8ebe631-2ea3-5d47-a461-2c01c7e21d38) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from purl2cpe mapping |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
pkg:github/git/git |
purl2cpe | 2026-06-01 10:15:42.853455 |
pkg:gitlab/gitlab-org/git |
purl2cpe | 2026-06-01 10:15:42.853457 |
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2025-48386 |
vulnerable | 2026-06-08 07:27:15.774099 |
Git allows a buffer overflow in 'wincred' credential helper
MEDIUM (6.3)
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. The wincred credential helper uses a static buffer (target) as a unique key for storing and comparing against internal storage. This credential helper does not properly bounds check the available space remaining in the buffer before appending to it with wcsncat(), leading to potential buffer overflows. 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.
Published: 2025-07-08T18:23:41.246Z
Updated: 2025-11-04T21:11:02.964Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2025-48385 |
vulnerable | 2026-06-08 07:27:15.773816 |
Git alllows arbitrary file writes via bundle-uri parameter injection
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.
Published: 2025-07-08T18:23:44.405Z
Updated: 2025-11-04T21:11:01.641Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2025-48384 |
vulnerable | 2026-06-08 07:27:15.771578 |
Git allows arbitrary code execution through broken config quoting
HIGH (8.1)
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 reading a config value, Git strips any trailing carriage return and line feed (CRLF). When writing a config entry, values with a trailing CR are not quoted, causing the CR to be lost when the config is later read. When initializing a submodule, if the submodule path contains a trailing CR, the altered path is read resulting in the submodule being checked out to an incorrect location. If a symlink exists that points the altered path to the submodule hooks directory, and the submodule contains an executable post-checkout hook, the script may be unintentionally executed after checkout. 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.
Published: 2025-07-08T18:23:48.710Z
Updated: 2026-02-26T17:51:05.174Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2024-52006 |
vulnerable | 2026-06-08 06:52:14.569902 |
Newline confusion in credential helpers can lead to credential exfiltration in git
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. Git defines a line-based protocol that is used to exchange information between Git and Git credential helpers. Some ecosystems (most notably, .NET and node.js) interpret single Carriage Return characters as newlines, which renders the protections against CVE-2020-5260 incomplete for credential helpers that treat Carriage Returns in this way. This issue has been addressed in commit `b01b9b8` which is included in release versions v2.48.1, v2.47.2, v2.46.3, v2.45.3, v2.44.3, v2.43.6, v2.42.4, v2.41.3, and v2.40.4. Users are advised to upgrade. Users unable to upgrade should avoid cloning from untrusted URLs, especially recursive clones.
Published: 2025-01-14T18:39:52.748Z
Updated: 2025-11-03T20:45:24.231Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2024-52005 |
vulnerable | 2026-06-08 06:52:14.569515 |
The sideband payload is passed unfiltered to the terminal in git
Git is a source code management tool. When cloning from a server (or fetching, or pushing), informational or error messages are transported from the remote Git process to the client via the so-called "sideband channel". These messages will be prefixed with "remote:" and printed directly to the standard error output. Typically, this standard error output is connected to a terminal that understands ANSI escape sequences, which Git did not protect against. Most modern terminals support control sequences that can be used by a malicious actor to hide and misrepresent information, or to mislead the user into executing untrusted scripts. As requested on the git-security mailing list, the patches are under discussion on the public mailing list. Users are advised to update as soon as possible. Users unable to upgrade should avoid recursive clones unless they are from trusted sources.
Published: 2025-01-15T17:35:02.379Z
Updated: 2025-01-15T20:10:36.473Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2024-50349 |
vulnerable | 2026-06-08 06:52:09.712400 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2024-32465 |
vulnerable | 2026-06-08 06:35:33.168132 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2024-32021 |
vulnerable | 2026-06-08 06:35:32.628315 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2024-32020 |
vulnerable | 2026-06-08 06:35:32.627234 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2024-32004 |
vulnerable | 2026-06-08 06:35:32.607200 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2024-32002 |
vulnerable | 2026-06-08 06:35:32.596527 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2023-29007 |
vulnerable | 2026-06-08 06:02:37.914801 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2023-25652 |
vulnerable | 2026-06-08 05:56:09.601812 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2023-23946 |
vulnerable | 2026-06-08 05:56:04.879450 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2023-22490 |
vulnerable | 2026-06-08 05:54:26.423412 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2022-41903 |
vulnerable | 2026-06-08 05:49:28.835330 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2022-39260 |
vulnerable | 2026-06-08 05:47:18.454742 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2022-39253 |
vulnerable | 2026-06-08 05:47:18.438415 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2022-29187 |
vulnerable | 2026-06-08 05:42:47.297861 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2022-23521 |
vulnerable | 2026-06-08 05:40:57.686259 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2021-21300 |
vulnerable | 2026-06-08 05:29:11.574434 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2020-5260 |
vulnerable | 2026-06-08 05:26:41.633012 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2020-11008 |
vulnerable | 2026-06-08 05:16:36.201658 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2019-1387 |
vulnerable | 2026-06-08 05:13:25.799882 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.