Integer overflow in `git archive`, `git log --format` leading to RCE in git
Git is distributed revision control system. `git log` can display commits in an arbitrary format using its `--format` specifiers. This functionality is also exposed to `git archive` via the `export-subst` gitattribute. When processing the padding operators, there is a integer overflow in `pretty.c::format_and_pad_commit()` where a `size_t` is stored improperly as an `int`, and then added as an offset to a `memcpy()`. This overflow can be triggered directly by a user running a command which invokes the commit formatting machinery (e.g., `git log --format=...`). It may also be triggered indirectly through git archive via the export-subst mechanism, which expands format specifiers inside of files within the repository during a git archive. This integer overflow can result in arbitrary heap writes, which may result in arbitrary code execution. The problem has been patched in the versions published on 2023-01-17, going back to v2.30.7. Users are advised to upgrade. Users who are unable to upgrade should disable `git archive` in untrusted repositories. If you expose git archive via `git daemon`, disable it by running `git config --global daemon.uploadArch false`.
- BDU:2023-00609
- ALSA-2023:0610
- ALSA-2023:0611
- DLA-3282-1
- DSA-5332-1
- openSUSE-SU-2024:12625-1
- RHSA-2023:0596
- RHSA-2023:0597
- RHSA-2023:0599
- RHSA-2023:0609
- RHSA-2023:0610
- RHSA-2023:0611
- RHSA-2023:0627
- RHSA-2023:0628
- RHSA-2023:0978
- RHSA-2023:1677
- RLSA-2023:0610
- RLSA-2023:0611
- SUSE-SU-2023:0108-1
- SUSE-SU-2023:0109-1
- Published
- Jan 17, 2023
- Updated
- Jun 17, 2026
- EPSS
- 44.3% · 99th percentile
- CWE
- CWE-190
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
52
Plan
Add it to your regular patch cycle.
- CVSS
- 39 / 40 · 9.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 13 / 30 · 44.3%
CISA SSVC decision
- Exploitation
- none
- Automatable
- yes
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 9.8
- CNA · GitHub_M
- 9.8
- agree
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for the hundreds of thousands of vulnerabilities in the database; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for helpAffected systems
| Vendor | Product | CPE |
|---|---|---|
| git-scm | git | cpe:2.3:a:git-scm:git |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- git-scm gitup to 2.30.6 inclusive
- git-scm git2.31.0 and later · up to 2.31.5 inclusive
- git-scm git2.32.0 and later · up to 2.32.4 inclusive
- git-scm git2.33.0 and later · up to 2.33.5 inclusive
- git-scm git2.34.0 and later · up to 2.34.5 inclusive
- git-scm git2.35.0 and later · up to 2.35.5 inclusive
- git-scm git2.36.0 and later · up to 2.36.3 inclusive
- git-scm git2.37.0 and later · up to 2.37.4 inclusive
- git-scm git2.38.0 and later · up to 2.38.2 inclusive
- git-scm git2.39.0
Versions reported by the vendor
Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.
git git
- < 2.30.7, >= 2.31.0, < 2.31.6, >= 2.32.0, < 2.32.5, >= 2.33.0, < 2.33.6, >= 2.34.0, < 2.34.6, >= 2.35.0, < 2.35.6, >= 2.36.0, < 2.36.4, >= 2.37.0, < 2.37.5, >= 2.38.0, < 2.38.3, = 2.39.0affected
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| AlmaLinux:8 | git | before 2.31.1-3.el8_7 | 2.31.1-3.el8_7 |
| AlmaLinux:8 | git-all | before 2.31.1-3.el8_7 | 2.31.1-3.el8_7 |
| AlmaLinux:8 | git-core | before 2.31.1-3.el8_7 | 2.31.1-3.el8_7 |
| AlmaLinux:8 | git-core-doc | before 2.31.1-3.el8_7 | 2.31.1-3.el8_7 |
| AlmaLinux:8 | git-credential-libsecret | before 2.31.1-3.el8_7 | 2.31.1-3.el8_7 |
| AlmaLinux:8 | git-daemon | before 2.31.1-3.el8_7 | 2.31.1-3.el8_7 |
| AlmaLinux:8 | git-email | before 2.31.1-3.el8_7 | 2.31.1-3.el8_7 |
| AlmaLinux:8 | git-gui | before 2.31.1-3.el8_7 | 2.31.1-3.el8_7 |
| AlmaLinux:8 | git-instaweb | before 2.31.1-3.el8_7 | 2.31.1-3.el8_7 |
| AlmaLinux:8 | git-subtree | before 2.31.1-3.el8_7 | 2.31.1-3.el8_7 |
| AlmaLinux:8 | git-svn | before 2.31.1-3.el8_7 | 2.31.1-3.el8_7 |
| AlmaLinux:8 | gitk | before 2.31.1-3.el8_7 | 2.31.1-3.el8_7 |
| AlmaLinux:8 | gitweb | before 2.31.1-3.el8_7 | 2.31.1-3.el8_7 |
| AlmaLinux:8 | perl-Git | before 2.31.1-3.el8_7 | 2.31.1-3.el8_7 |
| AlmaLinux:8 | perl-Git-SVN | before 2.31.1-3.el8_7 | 2.31.1-3.el8_7 |
| AlmaLinux:9 | git | before 2.31.1-3.el9_1 | 2.31.1-3.el9_1 |
| AlmaLinux:9 | git-all | before 2.31.1-3.el9_1 | 2.31.1-3.el9_1 |
| AlmaLinux:9 | git-core | before 2.31.1-3.el9_1 | 2.31.1-3.el9_1 |
| AlmaLinux:9 | git-core-doc | before 2.31.1-3.el9_1 | 2.31.1-3.el9_1 |
| AlmaLinux:9 | git-credential-libsecret | before 2.31.1-3.el9_1 | 2.31.1-3.el9_1 |
| AlmaLinux:9 | git-daemon | before 2.31.1-3.el9_1 | 2.31.1-3.el9_1 |
| AlmaLinux:9 | git-email | before 2.31.1-3.el9_1 | 2.31.1-3.el9_1 |
| AlmaLinux:9 | git-gui | before 2.31.1-3.el9_1 | 2.31.1-3.el9_1 |
| AlmaLinux:9 | git-instaweb | before 2.31.1-3.el9_1 | 2.31.1-3.el9_1 |
+96
Same product
git-scm: all recordsOther highest-scoring records for the same primary product.
- CVE-2018-17456Git before 2.14.5, 2.15.x before 2.15.3, 2.16.x before 2.16.5, 2.17.x before 2.17.2, 2.18.x before 2.18.1, and 2.19.x before 2.19.1 allows r68This week
- CVE-2025-48384Git allows arbitrary code execution through broken config quotingKEV63This week
- CVE-2017-1000117A malicious third-party can give a crafted "ssh://..." URL to an unsuspecting victim, and an attempt to visit the URL can result in any prog58Plan
- CVE-2021-21300malicious repositories can execute remote code while cloning57Plan
- CVE-2022-23521gitattributes parsing integer overflow in git56Plan
- CVE-2023-25652"git apply --reject" partially-controlled arbitrary file write46Plan
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| almalinux:git | 2.31.1-3.el8_7 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:git-all | 2.31.1-3.el8_7 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:git-core | 2.31.1-3.el8_7 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:git-core-doc | 2.31.1-3.el8_7 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:git-credential-libsecret | 2.31.1-3.el8_7 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:git-daemon | 2.31.1-3.el8_7 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:git-email | 2.31.1-3.el8_7 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:git-gui | 2.31.1-3.el8_7 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:git-instaweb | 2.31.1-3.el8_7 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:git-subtree | 2.31.1-3.el8_7 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:git-svn | 2.31.1-3.el8_7 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:gitk | 2.31.1-3.el8_7 · AlmaLinux:8 | Package registry (OSV) |
| alpine:git | 2.32.5-r0 · Alpine:v3.14 | Package registry (OSV) |
| debian:git | 1:2.39.1-0.1 · Debian:12 | Package registry (OSV) |
| opensuse:git | 2.26.2-150000.44.1 · openSUSE:Leap 15.4 | Package registry (OSV) |
| red hat:git | 0:2.27.0-3.el8_4 · Red Hat:rhel_eus:8.4::appstream | Package registry (OSV) |
| red hat:git-all | 0:2.27.0-3.el8_4 · Red Hat:rhel_eus:8.4::appstream | Package registry (OSV) |
| red hat:git-core | 0:2.27.0-3.el8_4 · Red Hat:rhel_eus:8.4::appstream | Package registry (OSV) |
| red hat:git-core-debuginfo | 0:2.27.0-3.el8_4 · Red Hat:rhel_eus:8.4::appstream | Package registry (OSV) |
| red hat:git-core-doc | 0:2.27.0-3.el8_4 · Red Hat:rhel_eus:8.4::appstream | Package registry (OSV) |
| red hat:git-credential-libsecret | 0:2.27.0-3.el8_4 · Red Hat:rhel_eus:8.4::appstream | Package registry (OSV) |
| red hat:git-credential-libsecret-debuginfo | 0:2.27.0-3.el8_4 · Red Hat:rhel_eus:8.4::appstream | Package registry (OSV) |
| red hat:git-daemon | 0:2.27.0-3.el8_4 · Red Hat:rhel_eus:8.4::appstream | Package registry (OSV) |
| red hat:git-daemon-debuginfo | 0:2.27.0-3.el8_4 · Red Hat:rhel_eus:8.4::appstream | Package registry (OSV) |
| red hat:git-debuginfo | 0:2.27.0-3.el8_4 · Red Hat:rhel_eus:8.4::appstream | Package registry (OSV) |
| red hat:git-debugsource | 0:2.27.0-3.el8_4 · Red Hat:rhel_eus:8.4::appstream | Package registry (OSV) |
| red hat:git-email | 0:2.27.0-3.el8_4 · Red Hat:rhel_eus:8.4::appstream | Package registry (OSV) |
| rocky linux:git | 0:2.31.1-3.el8_7 · Rocky Linux:8 | Package registry (OSV) |
| suse:git | 2.26.2-150000.44.1 · SUSE:Linux Enterprise High Performance Computing 15 SP1-LTSS | Package registry (OSV) |
Exploit status
Proof of concept available
A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.
Evidence
- Proof-of-concept repository on GitHub ×1
Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.
| Source | Kind | Date |
|---|---|---|
| Proof-of-concept repository on GitHub | stars:0 | 2023-01-26 |
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
- Published
- First PoC+8 d
- TodaySep 30, 2026+1352 d
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-190 · Integer Overflow or WraparoundCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
- git-scm.com/book/en/v2/Customizing-Git-Git-Attributes#_export_subst
- git-scm.com/docs/pretty-formats#Documentation/pretty-formats.txt-emltltNgttruncltruncmtruncem
- github.com/git/git/commit/508386c6c5857b4faa2c3e491f422c98cc69ae76
- github.com/git/git/security/advisories/GHSA-475x-2q3q-hvwq
- security.gentoo.org/glsa/202312-15
Vendor advisories and official records. Exploit/PoC links are deliberately left out.