CVE-2023-29007

HIGHNVD 7.87.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

This high-severity CVE scores 7.8 under NVD CVSS v3. EPSS exploit probability: 5.6% (93rd percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3
Elevated

Also known asEUVD-2023-32622 (ENISA EUVD)Source: ENISA EUVD

7.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • Public exploit or proof-of-concept code is available
CISA-KEV: Not listedEPSS PROB: 5.6%CVSS: 7.8Exploit: Public PoCExposed services: Not assessed

A fix is available — apply it.

Git is a revision control system. Prior to versions 2.30.9, 2.31.8, 2.32.7, 2.33.8, 2.34.8, 2.35.8, 2.36.6, 2.37.7, 2.38.5, 2.39.3, and 2.40.1, a specially crafted .gitmodules file with submodule URLs that are longer than 1024 characters can used to exploit a bug in config.c::git_config_copy_or_rename_section_in_file(). This bug can be used to inject arbitrary configuration into a user's $GIT_DIR/config when attempting to remove the configuration section associated with that submodule. When the attacker injects configuration values which specify executables to run (such as core.pager, core.editor, core.sshCommand, etc.) this can lead to a remote code execution. A fix A fix is available in versions 2.30.9, 2.31.8, 2.32.7, 2.33.8, 2.34.8, 2.35.8, 2.36.6, 2.37.7, 2.38.5, 2.39.3, and 2.40.1. As a workaround, avoid running git submodule deinit on untrusted repositories or without prior inspection of any submodule sections in $GIT_DIR/config.

CVSS v3
7.8
EG Score
7.8HIGHmedium confidence
EG Risk
51
EG Risk 51/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity78% × 45%
Impact severity (EG Severity): CVSS 7.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
5.6%
EPSS %ILE
93rd
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.8): severity, escalated by confirmed exploitation. This CVE's 7.8 is its impact severity (EG Severity), not escalated.

EG Severity
7.8 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
5.6% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-08). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

April 25, 2023

Last Modified

November 2, 2026

Advisory Details (8)

Auto-updated Oct 28, 2026
Patch available. Sources: github_commit, github.
GitHub commit

commit 528290f8c612 (git/git)

Fix landed in git/git commit 528290f8c612 — awaiting tagged release

https://github.com/git/git/commit/528290f8c61222433a8cf02fb7cfffa8438432b4
Web page

git/Documentation/RelNotes/2.30.9.txt at 9ce9dea4e1c2419cca126d29fa7730baa078a11b · git/git · GitHub

https://github.com/git/git/blob/9ce9dea4e1c2419cca126d29fa7730baa078a11b/Documentation/RelNotes/2.30.9.txt
Web page

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

https://security.gentoo.org/glsa/202312-15
Web page

[SECURITY] Fedora 37 Update: git-2.40.1-1.fc37 - package-announce - Fedora mailing-lists

https://lists.fedoraproject.org/archives/list/[email protected]/message/YFZWGQKB6MM5MNF2DLFTD7KS2KWPICKL/
Web page

[SECURITY] Fedora 36 Update: git-2.40.1-1.fc36 - package-announce - Fedora mailing-lists

https://lists.fedoraproject.org/archives/list/[email protected]/message/RKOXOAZ42HLXHXTW6JZI4L5DAIYDTYCU/
Web page

[SECURITY] Fedora 38 Update: git-2.40.1-1.fc38 - package-announce - Fedora mailing-lists

https://lists.fedoraproject.org/archives/list/[email protected]/message/PI7FZ4NNR5S5J5K6AMVQBH2JFP6NE4L7/
Web pageMentions a patch (unverified)

[SECURITY] [DLA 3844-1] git security update

https://lists.debian.org/debian-lts-announce/2024/06/msg00018.html
GitHub advisoryMentions a patch (unverified)

Arbitrary configuration injection via `git submodule deinit` · Advisory · git/git · GitHub

https://github.com/git/git/security/advisories/GHSA-v48j-4xgg-4844

Vendor Advisories for CVE-2023-29007(10)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(11)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntugit-email (1:2.25.1-1ubuntu3.11) @ focal2026-11-02ubuntu
ubuntugitweb (1:2.7.4-0ubuntu1.10+esm7) @ xenial2026-11-02ubuntu
redhatgit-0:2.18.4-4.el8_22023-05-31redhat
redhatgit-0:1.8.3.1-25.el7_92023-05-23redhat
redhatrh-git227-git-0:2.27.0-6.el72023-05-23redhat
redhatgit-0:2.31.1-4.el8_62023-05-22redhat
redhatgit-0:2.39.3-1.el8_82023-05-22redhat
redhatgit-0:2.39.3-1.el9_22023-05-22redhat
redhatgit-0:2.31.1-5.el9_02023-05-22redhat
redhatgit-0:2.27.0-4.el8_42023-05-22redhat
redhatgit-0:2.18.4-3.el8_12023-05-17redhat

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.

Affected Packages

(16 across 16 ecosystems)
Alpine:v3.14(1)
PackageVulnerable rangeFix by version rangeDependents
git—
  • 2.31.0 up to 2.32.7-r0: fixed in 2.32.7-r0
—
Alpine:v3.15(1)
PackageVulnerable rangeFix by version rangeDependents
git—
  • 2.31.0 up to 2.34.8-r0: fixed in 2.34.8-r0
—
Alpine:v3.16(1)
PackageVulnerable rangeFix by version rangeDependents
git—
  • 2.31.0 up to 2.36.6-r0: fixed in 2.36.6-r0
—
Alpine:v3.17(1)
PackageVulnerable rangeFix by version rangeDependents
git—
  • 2.31.0 up to 2.38.5-r0: fixed in 2.38.5-r0
—
Alpine:v3.18(1)
PackageVulnerable rangeFix by version rangeDependents
git—
  • 2.31.0 up to 2.40.1-r0: fixed in 2.40.1-r0
—
Alpine:v3.19(1)
PackageVulnerable rangeFix by version rangeDependents
git—
  • 2.31.0 up to 2.40.1-r0: fixed in 2.40.1-r0
—
Alpine:v3.20(1)
PackageVulnerable rangeFix by version rangeDependents
git—
  • 2.31.0 up to 2.40.1-r0: fixed in 2.40.1-r0
—
Alpine:v3.21(1)
PackageVulnerable rangeFix by version rangeDependents
git—
  • 2.31.0 up to 2.40.1-r0: fixed in 2.40.1-r0
—
Alpine:v3.22(1)
PackageVulnerable rangeFix by version rangeDependents
git—
  • 2.31.0 up to 2.40.1-r0: fixed in 2.40.1-r0
—
Alpine:v3.23(1)
PackageVulnerable rangeFix by version rangeDependents
git—
  • 2.31.0 up to 2.40.1-r0: fixed in 2.40.1-r0
—
Alpine:v3.24(1)
PackageVulnerable rangeFix by version rangeDependents
git—
  • 2.31.0 up to 2.40.1-r0: fixed in 2.40.1-r0
—
Debian:10(1)
PackageVulnerable rangeFix by version rangeDependents
git1:2.20.1-2 ... 1:2.20.1-2+deb10u8 (9 versions)
  • every version up to 1:2.20.1-2+deb10u9: fixed in 1:2.20.1-2+deb10u9
—
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
git1:2.30.2-1, 1:2.30.2-1+deb11u1, 1:2.30.2-1+deb11u2
  • every version up to 1:2.30.2-1+deb11u3: fixed in 1:2.30.2-1+deb11u3
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
git1:2.39.2+next.20230215-1, 1:2.39.2-1.1
  • every version up to 1:2.39.5-0+deb12u1: fixed in 1:2.39.5-0+deb12u1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
git—
  • every version up to 1:2.40.1-1: fixed in 1:2.40.1-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
git—
  • every version up to 1:2.40.1-1: fixed in 1:2.40.1-1
—

Weakness Classification(1)

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

Additional Vendor Advisories

(2)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 8× in last 7d / 35× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 232 rows on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 132 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-12 16:30 UTCEPSS rescoreEPSS 5.6% · 93rd percentile
  2. 2026-11-11 16:33 UTCEPSS rescoreEPSS 5.6% · 93rd percentile
  3. 2026-11-10 16:37 UTCEPSS rescoreEPSS 5.6% · 92nd percentile
  4. 2026-11-09 16:30 UTCEPSS rescoreEPSS 5.6% · 92nd percentile
  5. 2026-11-09 12:18 UTCEchelonGraph re-scored
  6. 2026-11-09 12:18 UTCVendor advisory
  7. 2026-11-08 16:34 UTCEPSS rescoreEPSS 5.6% · 92nd percentile
  8. 2026-11-07 16:34 UTCEPSS rescoreEPSS 5.6% · 92nd percentile
  9. 2026-11-06 16:31 UTCEPSS rescoreEPSS 5.6% · 92nd percentile
  10. 2026-11-05 16:33 UTCEPSS rescoreEPSS 5.6% · 92nd percentile
  11. 2026-11-04 16:31 UTCEPSS rescoreEPSS 5.6% · 92nd percentile
  12. 2026-11-03 16:40 UTCEPSS rescoreEPSS 5.6% · 92nd percentile
  13. 2026-11-02 23:26 UTCEchelonGraph re-scored▲ 0.80
  14. 2026-11-02 23:26 UTCVendor advisory
  15. 2026-11-02 23:26 UTCNVD updateCVSS v3 → 7.8
  16. 2026-11-02 22:38 UTCEchelonGraph re-scored
  17. 2026-11-02 22:38 UTCVendor advisory
  18. 2026-11-02 16:39 UTCEPSS rescoreEPSS 5.6% · 92nd percentile
  19. 2026-10-31 16:29 UTCEPSS rescoreEPSS 5.6% · 92nd percentile
  20. 2026-10-30 16:31 UTCEPSS rescoreEPSS 5.6% · 92nd percentile
  21. 2026-10-29 16:30 UTCEPSS rescoreEPSS 5.6% · 92nd percentile
  22. 2026-10-28 16:29 UTCEPSS rescoreEPSS 5.6% · 92nd percentile
  23. 2026-10-28 02:03 UTCEchelonGraph re-scored
  24. 2026-10-28 02:03 UTCVendor advisory
  25. 2026-10-27 16:29 UTCEPSS rescoreEPSS 5.6% · 92nd percentile
Show 75 more
  1. 2026-10-26 16:28 UTCEPSS rescoreEPSS 5.6% · 92nd percentile
  2. 2026-10-25 17:44 UTCEchelonGraph re-scored
  3. 2026-10-25 16:29 UTCEPSS rescoreEPSS 5.6% · 92nd percentile
  4. 2026-10-24 16:29 UTCEPSS rescoreEPSS 5.6% · 92nd percentile
  5. 2026-10-23 16:29 UTCEPSS rescoreEPSS 5.6% · 92nd percentile
  6. 2026-10-22 16:31 UTCEPSS rescoreEPSS 5.6% · 92nd percentile
  7. 2026-10-21 16:29 UTCEPSS rescoreEPSS 5.6% · 92nd percentile
  8. 2026-10-21 04:20 UTCEchelonGraph re-scored
  9. 2026-10-21 04:20 UTCVendor advisory
  10. 2026-10-20 16:29 UTCEPSS rescoreEPSS 5.6% · 92nd percentile
  11. 2026-10-19 16:29 UTCEPSS rescoreEPSS 5.6% · 92nd percentile
  12. 2026-10-18 16:29 UTCEPSS rescoreEPSS 5.6% · 92nd percentile
  13. 2026-10-18 08:06 UTCEchelonGraph re-scored
  14. 2026-10-17 16:29 UTCEPSS rescoreEPSS 5.6% · 92nd percentile
  15. 2026-10-16 16:35 UTCEPSS rescoreEPSS 5.6% · 92nd percentile
  16. 2026-10-15 16:29 UTCEPSS rescoreEPSS 5.6% · 92nd percentile
  17. 2026-10-14 16:29 UTCEPSS rescoreEPSS 5.6% · 92nd percentile
  18. 2026-10-13 16:29 UTCEPSS rescoreEPSS 5.6% · 92nd percentile
  19. 2026-10-12 18:29 UTCEchelonGraph re-scored
  20. 2026-10-12 16:30 UTCEPSS rescoreEPSS 5.9% · 93rd percentile
  21. 2026-10-11 21:55 UTCEchelonGraph re-scored
  22. 2026-10-11 13:45 UTCEPSS rescoreEPSS 6.1% · 93rd percentile
  23. 2026-10-10 19:57 UTCEPSS rescoreEPSS 6.1% · 93rd percentile
  24. 2026-10-09 22:03 UTCOSV refresh
  25. 2026-10-09 20:05 UTCEPSS rescoreEPSS 6.1% · 93rd percentile
  26. 2026-10-08 17:06 UTCEPSS rescoreEPSS 6.1% · 93rd percentile
  27. 2026-10-07 23:45 UTCEPSS rescoreEPSS 6.1% · 93rd percentile
  28. 2026-10-06 15:15 UTCEPSS rescoreEPSS 6.1% · 93rd percentile
  29. 2026-10-05 17:41 UTCEPSS rescoreEPSS 6.1% · 93rd percentile
  30. 2026-10-04 23:20 UTCEPSS rescoreEPSS 6.1% · 93rd percentile
  31. 2026-10-03 14:23 UTCEPSS rescoreEPSS 6.1% · 93rd percentile
  32. 2026-10-02 16:23 UTCEPSS rescoreEPSS 6.1% · 93rd percentile
  33. 2026-10-01 19:47 UTCEPSS rescoreEPSS 6.1% · 93rd percentile
  34. 2026-09-30 16:21 UTCEchelonGraph re-scored
  35. 2026-09-30 15:01 UTCEPSS rescoreEPSS 6.1% · 93rd percentile
  36. 2026-09-29 15:16 UTCEPSS rescoreEPSS 6.1% · 93rd percentile
  37. 2026-09-28 13:49 UTCEPSS rescoreEPSS 6.1% · 93rd percentile
  38. 2026-09-27 13:42 UTCEPSS rescoreEPSS 6.1% · 93rd percentile
  39. 2026-09-26 00:22 UTCEPSS rescoreEPSS 6.1% · 93rd percentile
  40. 2026-09-24 14:01 UTCEPSS rescoreEPSS 6.1% · 93rd percentile
  41. 2026-09-23 13:45 UTCEPSS rescoreEPSS 6.1% · 93rd percentile
  42. 2026-09-22 14:45 UTCEPSS rescoreEPSS 6.1% · 93rd percentile
  43. 2026-09-20 20:14 UTCEPSS rescoreEPSS 6.1% · 93rd percentile
  44. 2026-09-20 06:08 UTCOSV refresh
  45. 2026-09-16 14:05 UTCEPSS rescoreEPSS 6.1% · 93rd percentile
  46. 2026-09-13 16:44 UTCEPSS rescoreEPSS 6.1% · 92nd percentile
  47. 2026-09-12 14:58 UTCEPSS rescoreEPSS 6.1% · 92nd percentile
  48. 2026-09-11 14:50 UTCEPSS rescoreEPSS 6.1% · 92nd percentile
  49. 2026-09-11 09:34 UTCEPSS rescoreEPSS 6.1% · 92nd percentile
  50. 2026-09-08 21:57 UTCEPSS rescoreEPSS 6.1% · 92nd percentile
  51. 2026-09-07 15:59 UTCEPSS rescoreEPSS 6.1% · 92nd percentile
  52. 2026-09-06 13:45 UTCEPSS rescoreEPSS 6.1% · 92nd percentile
  53. 2026-09-05 15:25 UTCEPSS rescoreEPSS 6.1% · 93rd percentile
  54. 2026-09-04 13:58 UTCEPSS rescoreEPSS 6.1% · 92nd percentile
  55. 2026-09-04 05:04 UTCEPSS rescoreEPSS 6.1% · 92nd percentile
  56. 2026-09-02 14:09 UTCEPSS rescoreEPSS 6.1% · 92nd percentile
  57. 2026-09-01 13:51 UTCEPSS rescoreEPSS 6.1% · 92nd percentile
  58. 2026-09-01 09:29 UTCOSV refresh
  59. 2026-08-30 19:15 UTCEPSS rescoreEPSS 6.1% · 92nd percentile
  60. 2026-08-30 01:19 UTCEPSS rescoreEPSS 6.1% · 92nd percentile
  61. 2026-08-28 21:38 UTCEPSS rescoreEPSS 6.1% · 92nd percentile
  62. 2026-08-27 14:23 UTCEPSS rescoreEPSS 6.1% · 92nd percentile
  63. 2026-08-26 14:43 UTCEPSS rescoreEPSS 6.1% · 92nd percentile
  64. 2026-08-25 13:46 UTCEPSS rescoreEPSS 6.1% · 92nd percentile
  65. 2026-08-24 14:14 UTCEPSS rescoreEPSS 6.1% · 92nd percentile
  66. 2026-08-23 00:17 UTCEPSS rescoreEPSS 6.1% · 92nd percentile
  67. 2026-08-21 23:46 UTCEPSS rescoreEPSS 6.1% · 92nd percentile
  68. 2026-08-20 22:53 UTCEPSS rescoreEPSS 6.1% · 92nd percentile
  69. 2026-08-19 17:02 UTCEPSS rescoreEPSS 6.1% · 92nd percentile
  70. 2026-08-18 13:46 UTCEPSS rescoreEPSS 6.1% · 92nd percentile
  71. 2026-08-17 13:44 UTCEPSS rescoreEPSS 6.1% · 92nd percentile
  72. 2026-08-16 14:53 UTCEPSS rescoreEPSS 6.1% · 92nd percentile
  73. 2026-08-16 02:12 UTCEPSS rescoreEPSS 6.1% · 92nd percentile
  74. 2026-08-15 08:37 UTCOSV refresh
  75. 2026-08-15 01:28 UTCEPSS rescoreEPSS 6.1% · 92nd percentile

Publicly available exploits

(2 references)

Public exploit code is referenced for this CVE (2 GitHub PoCs). Defenders should treat patch urgency accordingly.

  • GitHub PoCx-Defender/CVE-2023-29007_win-version
    Published May 6, 2023
    Open source ↗
  • GitHub PoCethiack/CVE-2023-29007
    Published Apr 26, 2023

    PoC repository for CVE-2023-29007

    Open source ↗

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2023-29007?
CVE-2023-29007 is a high-severity vulnerability; its CVE record was published on April 25, 2023. Git is a revision control system. Prior to versions 2.30.9, 2.31.8, 2.32.7, 2.33.8, 2.34.8, 2.35.8, 2.36.6, 2.37.7, 2.38.5, 2.39.3, and 2.40.1, a specially crafted .gitmodules file with submodule URLs that are longer than 1024 characters can used to exploit a bug in…
When was the CVE record for CVE-2023-29007 published?
The CVE record for CVE-2023-29007 was published on April 25, 2023. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of November 2, 2026; the record at its source may have been updated since.
Is CVE-2023-29007 actively exploited?
CVE-2023-29007 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 5.6% probability of exploitation in the next 30 days (93rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2023-29007?
CVE-2023-29007 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2023-29007?
A fix for CVE-2023-29007 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2023-29007 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2023-29007

Explore →

Is Your Infrastructure Affected by CVE-2023-29007?

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

Book a Demo →Browse All CVEs