Evidence used
- No CISA KEV confirmation is currently recorded.
- EPSS is 1.02% for the current model date.
BlackTreeCVE IntelligenceFull vulnerability report · 2025
CVE-2025-48385High confidence
Git alllows arbitrary file writes via bundle-uri parameter injection
git · git
Official source article: GitHub GHSA-M98C-VGPC-9655 ↗. Check the applicable product and release in the original source.
8.6HighCVSS 4.0
Within 7 days
Patch availableHigh technical severity; prioritise exposed affected systems while verifying vendor guidance.
R
Open reassessment dashboard →Operational reassessment
Published severity in operational context
Published severityHigh→Operational priority:High, unchanged from published severity.unchanged
Compensating controls
- Validate the affected product branch and deploy the verified fixed release.
- Restrict the affected network interface to trusted sources where business-safe.
- Monitor vendor guidance and exploitation sources for a material change.
Verification
- Confirm that the asset runs git git and falls inside the recorded affected range.
- Verify the installed build against the product-specific fixed version after deployment.
- Validate exposure, authentication requirements and compensating controls in the actual environment.
- Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Distribution package intelligence
8 package statesRelease-specific package status
Alpine, Debian, ubuntu findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.
Repository candidate not checked
A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.
| Distribution release | Source package | Vendor state | Fixed version | Evidence |
|---|---|---|---|---|
| Alpine v3.23v3.23 · main | git | Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected. | 2.50.1-r0 | Alpine Security Database ↗Source updated 8 Oct 2026 |
| Alpine v3.22v3.22 · main | git | Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected. | 2.49.1-r0 | Alpine Security Database ↗Source updated 8 Oct 2026 |
| Alpine v3.21v3.21 · main | git | Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected. | 2.47.3-r0 | Alpine Security Database ↗Source updated 8 Oct 2026 |
| Debian trixietrixie · source | git | Vendor fix publishedDebian records a fixed source-package version for this release. | 1:2.47.3-0+deb13u1 | Debian Security Tracker ↗Source updated 8 Oct 2026 |
| Debian bookwormbookworm · source | git | Vendor fix publishedDebian records a fixed source-package version for this release. | 1:2.39.5-0+deb12u3 | Debian Security Tracker ↗Source updated 8 Oct 2026 |
| Debian forkyforky · source | git | Vendor fix publishedDebian records a fixed source-package version for this release. | 1:2.50.1-0.1 | Debian Security Tracker ↗Source updated 8 Oct 2026 |
| Debian sidsid · source | git | Vendor fix publishedDebian records a fixed source-package version for this release. | 1:2.50.1-0.1 | Debian Security Tracker ↗Source updated 8 Oct 2026 |
| Ubuntu 24.04 LTSnoble · standard archive | git | Vendor fix publishedCanonical reports that a fixed source package version has been published. Repository candidate availability is not checked by BlackTree. | 1:2.43.0-1ubuntu7.3 | Canonical Ubuntu Security ↗Source updated 7 Oct 2026 |
Direct vendor intelligence
1 currentAuthoritative vendor CSAF and VEX advisories
Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.
CVE-2025-48385 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitygit: Git arbitrary file writes
The vendor explicitly identifies these products as affected by this CVE.
- emacs-git as a component of Red Hat Enterprise Linux 6
- emacs-git-el as a component of Red Hat Enterprise Linux 6
- git as a component of Red Hat Enterprise Linux 6
- git-all as a component of Red Hat Enterprise Linux 6
- git-cvs as a component of Red Hat Enterprise Linux 6
- git-daemon as a component of Red Hat Enterprise Linux 6
- git-email as a component of Red Hat Enterprise Linux 6
- git-gui as a component of Red Hat Enterprise Linux 6
- git-svn as a component of Red Hat Enterprise Linux 6
- git.src as a component of Red Hat Enterprise Linux 6
- gitk as a component of Red Hat Enterprise Linux 6
- gitweb as a component of Red Hat Enterprise Linux 6
- Summary
- A bundled uri handling flaw was found in Git. 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.
- Remediation
- The RHEL-8 based Middleware Containers container images provided by this update can be downloaded from the Red Hat Container Registry at registry.access.redhat.com. Installation instructions for your platform are available at Red Hat Container Catalog (see References). Dockerfiles and scripts should be amended either to refer to this new image specifically, or to the latest image generally.
High technical severity; prioritise exposed affected systems while verifying vendor guidance.
Patch available01
What, why and how
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.
What
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.
Why
The product constructs a string for a command to be executed by a separate component in another control sphere, but it does not properly delimit the intended arguments, options, or switches within that command string.
How
An attacker operating through a network path may attempt exploitation when the stated preconditions are met. If successful, the issue may execute code or commands in the affected security context.
What
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.
Why
The product constructs a string for a command to be executed by a separate component in another control sphere, but it does not properly delimit the intended arguments, options, or switches within that command string.
How
An attacker operating through a network path may attempt exploitation when the stated preconditions are met. If successful, the issue may execute code or commands in the affected security context.
02
Exploit reality and attack path
CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.
Observed exploitation No confirmed evidence
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.
Public PoC / exploit material None recorded
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.
- Likely attack path
- a network path → Improper Neutralization of Argument Delimiters in a Command ('Argument Injection') → execute code or commands in the affected security context
- Attack surface
- Network
- Privileges required
- None: unauthenticated exploitation is possible
- User interaction
- Active interaction required
- Attack complexity
- Low: no specialised conditions are recorded
- Security boundary
- Not a CVSS 4.0 base metric
- Weakness
?
CWE means Common Weakness Enumeration: a standard category for the underlying weakness. - CWE-88 ↗
CWE-88: Improper Neutralization of Argument Delimiters in a Command ('Argument Injection'). The product constructs a string for a command to be executed by a separate component in another control sphere, but it does not properly delimit the intended arguments, options, or switches within that command string.
- CVSS vector
?
CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity. CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:NCommon Vulnerability Scoring System 4.0: the compact vector below is decoded into plain language.
AVNetworkAttack vector: The vulnerable component can be reached over a network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.ATNoneAttack requirements: No additional deployment or execution condition is required.PRNonePrivileges required: The attacker does not need an account or existing privileges.UIActiveUser interaction: A user must take a deliberate action for exploitation to succeed.VCHighVulnerable-system confidentiality: A successful attack can cause a major loss.VIHighVulnerable-system integrity: A successful attack can cause a major loss.VAHighVulnerable-system availability: A successful attack can cause a major loss.SCNoneSubsequent-system confidentiality: No direct loss is represented by this metric.SINoneSubsequent-system integrity: No direct loss is represented by this metric.SANoneSubsequent-system availability: No direct loss is represented by this metric.- Post-exploitation / living off the land
- After compromise, an attacker may use built-in shells, scripting engines, scheduled tasks and native network utilities for discovery, persistence or movement. This is a plausible LoTL path, not evidence that it has occurred for every attack.
03
Patch and workaround
Operational remediation based on structured source evidence.
- Status
?
Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change. - Patch available
- Affected
- emacs-git as a component of Red Hat Enterprise Linux 6
- emacs-git-el as a component of Red Hat Enterprise Linux 6
- git as a component of Red Hat Enterprise Linux 6
- git-all as a component of Red Hat Enterprise Linux 6
- git-cvs as a component of Red Hat Enterprise Linux 6
- git-daemon as a component of Red Hat Enterprise Linux 6
- git-email as a component of Red Hat Enterprise Linux 6
- git-gui as a component of Red Hat Enterprise Linux 6
- git-svn as a component of Red Hat Enterprise Linux 6
- git.src as a component of Red Hat Enterprise Linux 6
- gitk as a component of Red Hat Enterprise Linux 6
- gitweb as a component of Red Hat Enterprise Linux 6
- perl-Git as a component of Red Hat Enterprise Linux 6
- Fixed
- rhpam-7/rhpam-businesscentral-monitoring-rhel8@sha256:26a7fe83f3a34f02c2d0fdb0c67958166d79e47d264e7538e7c041c73af8406b_amd64 as a component of Middleware Containers for OpenShift
- rhpam-7/rhpam-businesscentral-rhel8@sha256:b4804f253e75441ba011a85a38673f1499b11df42e7d63a5d850e2e7f99c4f63_amd64 as a component of Middleware Containers for OpenShift
- rhpam-7/rhpam-controller-rhel8@sha256:b6344cd0cfa033dca638dffa1d6f05b1b44c49cec805a4bead4bb31e967152e7_amd64 as a component of Middleware Containers for OpenShift
- rhpam-7/rhpam-dashbuilder-rhel8@sha256:47dacb456c1349638195e8d1a13224f63c1675199fc819803b50b617b9442c60_amd64 as a component of Middleware Containers for OpenShift
- rhpam-7/rhpam-kieserver-rhel8@sha256:1b23a90b54af8f3d61cd9b1cad05cf30f0225af6d8cf1f833e21b0630623070a_amd64 as a component of Middleware Containers for OpenShift
- rhpam-7/rhpam-operator-bundle@sha256:b005ca81fb10121bed0422266e415164d58fc48d85e1fe5b4d36a3a222c249f1_amd64 as a component of Middleware Containers for OpenShift
- rhpam-7/rhpam-process-migration-rhel8@sha256:3c56a1235f0a61744b38b4b579b91b179ba07ae001ead41c64579bd9fd1b4f9c_amd64 as a component of Middleware Containers for OpenShift
- rhpam-7/rhpam-rhel8-operator@sha256:add1edfb633e14a4d23794b80ca0d3f96720d33e11c132580d7b58bf29f9a167_amd64 as a component of Middleware Containers for OpenShift
- rhpam-7/rhpam-smartrouter-rhel8@sha256:63fad8909d38e5f5e5bdb539f025bd95f1d2ec7cc6b6ee5e9b48e36036d19484_amd64 as a component of Middleware Containers for OpenShift
- rhcos-x86_64-413.92.202509030117-0 as a component of Red Hat OpenShift Container Platform 4.13
- rhcos-aarch64-414.92.202508270040-0 as a component of Red Hat OpenShift Container Platform 4.14
- rhcos-ppc64le-414.92.202508270040-0 as a component of Red Hat OpenShift Container Platform 4.14
- rhcos-s390x-414.92.202508270040-0 as a component of Red Hat OpenShift Container Platform 4.14
- rhcos-x86_64-414.92.202508270040-0 as a component of Red Hat OpenShift Container Platform 4.14
- rhcos-aarch64-415.92.202508192014-0 as a component of Red Hat OpenShift Container Platform 4.15
- rhcos-ppc64le-415.92.202508192014-0 as a component of Red Hat OpenShift Container Platform 4.15
- rhcos-s390x-415.92.202508192014-0 as a component of Red Hat OpenShift Container Platform 4.15
- rhcos-x86_64-415.92.202508192014-0 as a component of Red Hat OpenShift Container Platform 4.15
- rhcos-aarch64-416.94.202508261955-0 as a component of Red Hat OpenShift Container Platform 4.16
- rhcos-ppc64le-416.94.202508261955-0 as a component of Red Hat OpenShift Container Platform 4.16
- rhcos-s390x-416.94.202508261955-0 as a component of Red Hat OpenShift Container Platform 4.16
- rhcos-x86_64-416.94.202508261955-0 as a component of Red Hat OpenShift Container Platform 4.16
- rhcos-aarch64-417.94.202508141510-0 as a component of Red Hat OpenShift Container Platform 4.17
- rhcos-ppc64le-417.94.202508141510-0 as a component of Red Hat OpenShift Container Platform 4.17
- rhcos-s390x-417.94.202508141510-0 as a component of Red Hat OpenShift Container Platform 4.17
- rhcos-x86_64-417.94.202508141510-0 as a component of Red Hat OpenShift Container Platform 4.17
- rhcos@sha256:09d62510dd6eba82e954b888e107df450517479fbceecb6397b24aab72ada998_aarch64 as a component of Red Hat OpenShift Container Platform 4.18
- rhcos@sha256:09d62510dd6eba82e954b888e107df450517479fbceecb6397b24aab72ada998_ppc64le as a component of Red Hat OpenShift Container Platform 4.18
- rhcos@sha256:09d62510dd6eba82e954b888e107df450517479fbceecb6397b24aab72ada998_s390x as a component of Red Hat OpenShift Container Platform 4.18
- rhcos@sha256:09d62510dd6eba82e954b888e107df450517479fbceecb6397b24aab72ada998_x86_64 as a component of Red Hat OpenShift Container Platform 4.18
- and 315 more
- Action
- The RHEL-8 based Middleware Containers container images provided by this update can be downloaded from the Red Hat Container Registry at registry.access.redhat.com. Installation instructions for your platform are available at Red Hat Container Catalog (see References). Dockerfiles and scripts should be amended either to refer to this new image specifically, or to the latest image generally.
- Workaround
- No verified workaround is recorded. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.
04
Evidence and provenance
Published 8 Jul 2025 · Last source change 4 Nov 2025, 21:11 UTC · CWE-88 · Improper Neutralization of Argument Delimiters in a Command ('Argument Injection')
CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source FIRST · tracked since 2026-08-14
?
The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.European sourceENISA EUVD · EUVD-2025-20678
Product sourceVendor CSAF · Red Hat Product Security
Remediation sourceVendor CSAF · Red Hat Product Security
CWE sourceCNA
NVD statusNVD not scheduled
Core structured fields are present and their contributing authorities are shown above.
Material change intelligence
View recent updates ↗What changed after publication
- Affected versionsThe structured affected or fixed version information changed.Red Hat Product Security ↗
- Before
- < 2.43.7; >= 2.44.0-rc0, < 2.44.4; >= 2.45.0-rc0, < 2.45.4; >= 2.46.0-rc0, < 2.46.4; >= 2.47.0-rc0, < 2.47.3; >= 2.48.0-rc0, < 2.48.2; >= 2.49.0-rc0, < 2.49.1; >= 2.50.0-rc0, < 2.50.1 · Fixed: No fixed version is explicitly recorded in the structured CVE data.
- After
- < 2.43.7; >= 2.44.0-rc0, < 2.44.4; >= 2.45.0-rc0, < 2.45.4; >= 2.46.0-rc0, < 2.46.4; >= 2.47.0-rc0, < 2.47.3; >= 2.48.0-rc0, < 2.48.2; >= 2.49.0-rc0, < 2.49.1; >= 2.50.0-rc0, < 2.50.1 · Fixed: The RHEL-8 based Middleware Containers container images provided by this update can be downloaded from the Red Hat Container Registry at registry.access.redhat.com. Installation instructions for your platform are available at Red Hat Container Catalog (see References). Dockerfiles and scripts should be amended either to refer to this new image specifically, or to the latest image generally.
- Remediation statusRemediation status changed from Awaiting fix to Patch available.Red Hat Product Security ↗
- Before
- Awaiting fix
- After
- Patch available
CVE published
Fixed release recorded from official guidance
Technical terms and abbreviations used in this report
- CVE
- Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
- CVSS
- Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
- EPSS
- Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
- CWE
- Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
- CNA
- CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
- CISA ADP
- Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
- NVD
- National Vulnerability Database: NIST's enrichment service for CVE records.
- CERT / CSIRT
- A computer security incident response team that publishes warnings or coordinates incident response.
- PoC
- Proof of concept: public material that demonstrates or helps reproduce exploitation.
- CSAF
- Common Security Advisory Framework: a machine-readable format for security advisories.
- LoTL
- Living off the land: abuse of legitimate tools or system functions during an attack.