CVE-2022-41903

CRITICALNVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 44.3%, top 1% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Elevated
9.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 44%CVSS: 9.8Exploit: NoneExposed: 0

A fix is available — apply it.

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.

CVSS v3
9.8
EG Score
9.8(medium)
EG Risk
77(Track)
EG Risk 77/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity98% × 45%
Exploitation44% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
98.6%
KEV
Not listed

Published

January 17, 2023

Last Modified

November 21, 2024

Advisory Details (5)

Auto-updated Jun 9, 2026
Patch available. Sources: github_commit, github.
generic

Git: Multiple Vulnerabilities (GLSA 202312-15) — Gentoo security

https://security.gentoo.org/glsa/202312-15
github Patch Available

Heap overflow in `git archive`, `git log --format` leading to RCE · Advisory · git/git · GitHub

https://github.com/git/git/security/advisories/GHSA-475x-2q3q-hvwq
github_commit

commit 508386c6c585 (git/git)

Fix landed in git/git commit 508386c6c585 — awaiting tagged release

https://github.com/git/git/commit/508386c6c5857b4faa2c3e491f422c98cc69ae76
generic

Git - pretty-formats Documentation

https://git-scm.com/docs/pretty-formats#Documentation/pretty-formats.txt-emltltNgttruncltruncmtruncem
generic

Git - Git Attributes

https://git-scm.com/book/en/v2/Customizing-Git-Git-Attributes#_export_subst

Patch Availability(13)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntugit-email (1:2.37.2-1ubuntu1.2) @ kinetic2026-05-25ubuntu
ubuntugit-email (1:2.7.4-0ubuntu1.10+esm4) @ xenial2026-05-25ubuntu
ubuntugit-email (1:1.9.1-1ubuntu0.10+esm1) @ trusty2026-05-25ubuntu
redhatredhat-virtualization-host-0:4.5.3-202304051438_8.62023-04-10redhat
redhatgit-0:1.8.3.1-24.el7_92023-02-28redhat
redhatgit-0:2.31.1-3.el8_62023-02-07redhat
redhatgit-0:2.31.1-3.el9_02023-02-07redhat
redhatgit-0:2.18.4-3.el8_22023-02-06redhat
redhatgit-0:2.31.1-3.el8_72023-02-06redhat
redhatgit-0:2.27.0-3.el8_42023-02-06redhat
redhatgit-0:2.31.1-3.el9_12023-02-06redhat
redhatrh-git227-git-0:2.27.0-4.el72023-02-06redhat
redhatgit-0:2.18.4-2.el8_12023-02-06redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(14)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 13× in last 7d / 34× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-24 14:15 UTCEPSS rescore
  2. 2026-07-23 14:16 UTCEPSS rescore
  3. 2026-07-23 02:14 UTCEG score recompute
  4. 2026-07-22 23:01 UTCEG score recompute
  5. 2026-07-22 14:06 UTCEPSS rescore
  6. 2026-07-21 15:23 UTCEPSS rescore
  7. 2026-07-21 15:23 UTCEPSS rescore
  8. 2026-07-20 17:05 UTCEPSS rescore
  9. 2026-07-19 14:29 UTCEPSS rescore
  10. 2026-07-19 02:27 UTCEPSS rescore
  11. 2026-07-19 02:27 UTCEPSS rescore
  12. 2026-07-18 10:03 UTCEPSS rescore
  13. 2026-07-18 10:03 UTCEPSS rescore
  14. 2026-07-16 08:23 UTCOSV refresh
  15. 2026-07-15 16:56 UTCEPSS rescore
  16. 2026-07-15 16:56 UTCEPSS rescore
  17. 2026-07-15 01:58 UTCEPSS rescore
  18. 2026-07-13 22:28 UTCEPSS rescore
  19. 2026-07-13 06:11 UTCEPSS rescore
  20. 2026-07-12 05:44 UTCEPSS rescore
  21. 2026-07-11 08:25 UTCEPSS rescore
  22. 2026-07-11 08:25 UTCEPSS rescore
  23. 2026-07-09 19:08 UTCEPSS rescore
  24. 2026-07-06 16:25 UTCEPSS rescore
  25. 2026-07-04 06:29 UTCEPSS rescore
Show 63 more
  1. 2026-07-02 16:58 UTCEPSS rescore
  2. 2026-07-01 15:04 UTCEPSS rescore
  3. 2026-06-28 07:52 UTCOSV refresh
  4. 2026-06-28 04:54 UTCEPSS rescore
  5. 2026-06-28 04:54 UTCEPSS rescore
  6. 2026-06-27 03:07 UTCEPSS rescore
  7. 2026-06-27 03:07 UTCEPSS rescore
  8. 2026-06-25 13:48 UTCEPSS rescore
  9. 2026-06-25 13:48 UTCEPSS rescore
  10. 2026-06-24 14:03 UTCEPSS rescore
  11. 2026-06-23 21:31 UTCEPSS rescore
  12. 2026-06-23 21:31 UTCEPSS rescore
  13. 2026-06-21 01:58 UTCEPSS rescore
  14. 2026-06-21 01:58 UTCEPSS rescore
  15. 2026-06-18 17:51 UTCEPSS rescore
  16. 2026-06-18 17:51 UTCEPSS rescore
  17. 2026-06-17 17:51 UTCEPSS rescore
  18. 2026-06-17 17:51 UTCEPSS rescore
  19. 2026-06-16 17:51 UTCEPSS rescore
  20. 2026-06-15 17:46 UTCEPSS rescore
  21. 2026-06-14 23:16 UTCEPSS rescore
  22. 2026-06-13 22:59 UTCEPSS rescore
  23. 2026-06-12 23:10 UTCEPSS rescore
  24. 2026-06-12 23:10 UTCEPSS rescore
  25. 2026-06-11 13:58 UTCEPSS rescore
  26. 2026-06-11 13:58 UTCEPSS rescore
  27. 2026-06-10 22:17 UTCEPSS rescore
  28. 2026-06-10 18:47 UTCOSV refresh
  29. 2026-06-10 13:21 UTCEPSS rescore
  30. 2026-06-10 13:21 UTCEPSS rescore
  31. 2026-06-08 14:15 UTCEPSS rescore
  32. 2026-06-07 15:23 UTCEPSS rescore
  33. 2026-06-07 15:23 UTCEPSS rescore
  34. 2026-06-06 13:46 UTCEPSS rescore
  35. 2026-06-06 13:46 UTCEPSS rescore
  36. 2026-06-06 13:46 UTCEPSS rescore
  37. 2026-06-05 22:46 UTCEPSS rescore
  38. 2026-06-05 22:46 UTCEPSS rescore
  39. 2026-06-05 06:09 UTCEPSS rescore
  40. 2026-06-05 06:09 UTCEPSS rescore
  41. 2026-06-04 13:11 UTCEPSS rescore
  42. 2026-06-02 20:12 UTCEPSS rescore
  43. 2026-06-02 20:11 UTCEPSS rescore
  44. 2026-06-01 13:50 UTCEPSS rescore
  45. 2026-06-01 13:50 UTCEPSS rescore
  46. 2026-05-31 22:29 UTCEPSS rescore
  47. 2026-05-31 22:29 UTCEPSS rescore
  48. 2026-05-31 00:15 UTCEPSS rescore
  49. 2026-05-31 00:15 UTCEPSS rescore
  50. 2026-05-29 13:43 UTCEPSS rescore
  51. 2026-05-28 13:43 UTCEPSS rescore
  52. 2026-05-28 13:43 UTCEPSS rescore
  53. 2026-05-27 13:39 UTCEPSS rescore
  54. 2026-05-27 13:39 UTCEPSS rescore
  55. 2026-05-26 13:43 UTCEPSS rescore
  56. 2026-05-26 13:43 UTCEPSS rescore
  57. 2026-05-26 13:43 UTCEPSS rescore
  58. 2026-05-26 07:17 UTCEPSS rescore
  59. 2026-05-26 07:17 UTCEPSS rescore
  60. 2026-05-26 07:17 UTCEPSS rescore
  61. 2026-05-25 08:27 UTCEG score recompute
  62. 2026-05-25 08:27 UTCVendor advisory
  63. 2026-05-24 11:21 UTCOSV refresh

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2022-41903?
CVE-2022-41903 is a critical vulnerability published on January 17, 2023. 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…
When was CVE-2022-41903 disclosed?
CVE-2022-41903 was first published in the National Vulnerability Database on January 17, 2023, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2022-41903 actively exploited?
CVE-2022-41903 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 98.6% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2022-41903?
CVE-2022-41903 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2022-41903?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2022-41903, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2022-41903

Explore →

Is Your Infrastructure Affected by CVE-2022-41903?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs