CVE-2026-102827

CRITICALNVD 9.89.8
EchelonGraph scoreMEDIUM confidence

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

This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 0.6% (47th percentile of EPSS-scored CVEs). GitHub Security Advisory CVSS 8.1 is lower than this score; a lower GitHub score revises it only when its advisory is newer than the CVE record's last change, and this advisory (published 2026-10-05) is not newer than that change (2026-10-08), so it does not.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 3 sources updated this weekElevated

Also known asEUVD-2026-89333 (ENISA EUVD) · GHSA-858h-whjf-mvg5 (GitHub Security Advisories)Source: ENISA EUVD

9.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: 0.6%CVSS: 9.8Exploit: Public PoCExposed services: Not assessed

A fix is available — apply it.

simple-git, an interface for running git commands in any node.js application, enables applications to execute Git operations from JavaScript. Prior to 4.0.0, the default blockUnsafeOperationsPlugin compares parsed option names with literal dangerous option spellings while Git accepts unambiguous long-option abbreviations. Attacker-influenced push arguments such as abbreviated --receive-pack or --exec forms can therefore bypass detectVulnerableFlags, reach git push against a local or file remote or an attacker-influenced receive-pack target, and cause Git to invoke an attacker-selected command in consumers that expose those arguments. The clone-side abbreviation handling does not protect the push path. This issue is fixed in 4.0.0.

CVSS v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
60
EG Risk 60/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)
Severity98% × 45%
Impact severity (EG Severity): CVSS 9.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
0.6%
EPSS %ILE
47th
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 (9.8): severity, escalated by confirmed exploitation. This CVE's 9.8 is its impact severity (EG Severity), not escalated.

EG Severity
9.8 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
0.6% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). 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

September 29, 2026

Last Modified

October 8, 2026

Advisory Details (3)

Auto-updated Oct 30, 2026
🔬 Proof of concept available. Patch available. Sources: github_pr, github_release, github.
GitHub advisoryMentions a patch (unverified)🟡 PoC Available

unsafe-operations plugin bypass via git long-option abbreviation (--receive-p/--exe) -> command execution (residual of CVE-2026-28291) · Advisory · steveukx/git-js · GitHub

https://github.com/steveukx/git-js/security/advisories/GHSA-858h-whjf-mvg5
GitHub release Patch Available

simple-git@4.0.0

Patch available: steveukx/git-js simple-git@4.0.0

https://github.com/steveukx/git-js/releases/tag/simple-git@4.0.0
GitHub pull request Patch Available

V4

Patch available: steveukx/git-js simple-git@4.0.0 (PR #1193 merged 2026-09-23)

https://github.com/steveukx/git-js/pull/1193

Vendor Advisories for CVE-2026-102827(1)

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

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
npmsimple-git @ 4.0.0 (fixes <= 3.36.0)—ghsa

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

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFix by version rangeDependents
simple-git—
  • every version up to 4.0.0: fixed in 4.0.0
—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 15× in last 7d / 63× 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 it from the CNA feed. 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). Most recent first.

  1. 2026-11-01 16:33 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  2. 2026-11-01 14:52 UTCGHSA enrichmentGHSA-858h-whjf-mvg5 · GitHub severity HIGH · GitHub CVSS 8.1
  3. 2026-11-01 08:00 UTCGHSA enrichmentGHSA-858h-whjf-mvg5 · GitHub severity HIGH · GitHub CVSS 8.1
  4. 2026-11-01 08:00 UTCEG score recompute
  5. 2026-10-31 16:31 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  6. 2026-10-31 12:34 UTCEG score recompute
  7. 2026-10-30 16:33 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  8. 2026-10-30 10:16 UTCEG score recompute
  9. 2026-10-29 16:32 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  10. 2026-10-29 07:59 UTCEG score recompute
  11. 2026-10-28 16:31 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  12. 2026-10-28 05:41 UTCEG score recompute
  13. 2026-10-27 16:31 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  14. 2026-10-27 03:24 UTCEG score recompute
  15. 2026-10-26 16:30 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  16. 2026-10-25 21:01 UTCEG score recompute
  17. 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  18. 2026-10-25 14:56 UTCEG score recompute
  19. 2026-10-24 18:44 UTCEG score recompute
  20. 2026-10-24 16:31 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  21. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  22. 2026-10-23 16:27 UTCEG score recompute
  23. 2026-10-22 16:33 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  24. 2026-10-22 14:10 UTCEG score recompute
  25. 2026-10-21 16:31 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
Show 49 more
  1. 2026-10-21 11:48 UTCEG score recompute
  2. 2026-10-20 16:31 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  3. 2026-10-20 09:31 UTCEG score recompute
  4. 2026-10-19 16:31 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  5. 2026-10-19 07:14 UTCEG score recompute
  6. 2026-10-18 16:31 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  7. 2026-10-18 04:57 UTCEG score recompute
  8. 2026-10-17 16:33 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  9. 2026-10-17 02:37 UTCEG score recompute
  10. 2026-10-16 16:40 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  11. 2026-10-16 00:20 UTCEG score recompute
  12. 2026-10-15 16:31 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  13. 2026-10-14 18:47 UTCEG score recompute
  14. 2026-10-14 16:31 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  15. 2026-10-14 03:04 UTCEG score recompute
  16. 2026-10-13 16:33 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  17. 2026-10-12 16:40 UTCEG score recompute
  18. 2026-10-12 16:33 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  19. 2026-10-11 20:16 UTCEG score recompute
  20. 2026-10-11 18:18 UTCEG score recompute
  21. 2026-10-11 14:18 UTCEG score recompute
  22. 2026-10-11 13:47 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  23. 2026-10-10 22:47 UTCEG score recompute
  24. 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  25. 2026-10-09 23:33 UTCEG score recompute
  26. 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  27. 2026-10-08 20:21 UTCEG score recompute▲ 1.70
  28. 2026-10-08 20:15 UTCNVD updateCVSS v3 → 9.8 · severity → CRITICAL
  29. 2026-10-08 17:11 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  30. 2026-10-08 09:43 UTCEG score recompute
  31. 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  32. 2026-10-06 22:34 UTCEG score recompute
  33. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  34. 2026-10-05 23:11 UTCEG score recompute
  35. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  36. 2026-10-04 23:43 UTCEG score recompute
  37. 2026-10-04 23:21 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  38. 2026-10-04 00:21 UTCEG score recompute
  39. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  40. 2026-10-03 00:59 UTCEG score recompute
  41. 2026-10-02 13:18 UTCEG score recompute
  42. 2026-10-02 12:46 UTCEG score recompute
  43. 2026-10-02 07:05 UTCEG score recompute
  44. 2026-10-01 19:49 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  45. 2026-09-30 18:47 UTCEG score recompute
  46. 2026-09-30 15:02 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  47. 2026-09-29 19:20 UTCEG score recompute
  48. 2026-09-29 18:50 UTCEG score recomputeFirst assessed: 8.1 HIGH
  49. 2026-09-29 18:48 UTCMITRE cvelistV5first tracked

Publicly available exploits

(1 reference)

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

  • GitHub PoCD7EAD/CVE-2026-102827
    Published Oct 13, 2026

    Command execution and patch bypass of CVE-2026-28291 in git-js.

    Open source ↗

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-102827?
CVE-2026-102827 is a critical-severity vulnerability; its CVE record was published on September 29, 2026. simple-git, an interface for running git commands in any node.js application, enables applications to execute Git operations from JavaScript. Prior to 4.0.0, the default blockUnsafeOperationsPlugin compares parsed option names with literal dangerous option spellings while Git accepts unambiguous…
When was the CVE record for CVE-2026-102827 published?
The CVE record for CVE-2026-102827 was published on September 29, 2026. 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 October 8, 2026; the record at its source may have been updated since.
Is CVE-2026-102827 actively exploited?
CVE-2026-102827 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% probability of exploitation in the next 30 days (47th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-102827?
CVE-2026-102827 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2026-102827?
A fix for CVE-2026-102827 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-102827 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-2026-102827

Explore →

Is Your Infrastructure Affected by CVE-2026-102827?

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

Book a Demo →Browse All CVEs