CVE-2026-62371

HIGHPre-NVD 8.88.8
EchelonGraph scoreMEDIUM confidence

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

Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-09-22. A secondary CVSS source baseline 8.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 3 sources updated this week

Also known asEUVD-2026-84003 (ENISA EUVD) · GHSA-5jpj-293f-rhvj (GitHub Security Advisories)Source: ENISA EUVD

8.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 8.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

KubeEdge is an open source system for extending native containerized application orchestration capabilities to hosts at Edge. From 1.12.0 until 1.21.2, 1.22.2, and 1.23.1, the v1alpha2 NodeUpgradeJob handler in edge/pkg/taskmanager/actions/nodeupgradejob.go concatenates authenticated user-controlled spec.version and spec.image values into the keadm upgrade edge shell command. A user with permission to create or update NodeUpgradeJob resources can supply shell metacharacters in either field, causing arbitrary commands to execute on targeted edge nodes with the privileges of the upgrade process and compromising node confidentiality, integrity, and availability. This issue is fixed in versions 1.21.2, 1.22.2, and 1.23.1.

CVSS v3
8.8
EG Score
8.8HIGHmedium confidence
EG Risk
40
EG Risk 40/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)
Severity88% × 45%
Impact severity (EG Severity): CVSS 8.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.5% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
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.5%
EPSS %ILE
41st
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 (8.8): severity, escalated by confirmed exploitation. This CVE's 8.8 is its impact severity (EG Severity), not escalated.

EG Severity
8.8 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.5% 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 21, 2026

Last Modified

September 24, 2026

Advisory Details (10)

Auto-updated Sep 21, 2026
Patch available. Sources: github, github_pr, github_commit.
Web page

kubeedge/CHANGELOG/CHANGELOG-1.23.md at master · kubeedge/kubeedge · GitHub

https://github.com/kubeedge/kubeedge/blob/master/CHANGELOG/CHANGELOG-1.23.md
Web page

kubeedge/CHANGELOG/CHANGELOG-1.22.md at master · kubeedge/kubeedge · GitHub

https://github.com/kubeedge/kubeedge/blob/master/CHANGELOG/CHANGELOG-1.22.md
Web page

kubeedge/CHANGELOG/CHANGELOG-1.21.md at master · kubeedge/kubeedge · GitHub

https://github.com/kubeedge/kubeedge/blob/master/CHANGELOG/CHANGELOG-1.21.md
GitHub commit

commit b72db7f8a0f7 (kubeedge/kubeedge)

Fix landed in kubeedge/kubeedge commit b72db7f8a0f7 — awaiting tagged release

https://github.com/kubeedge/kubeedge/commit/b72db7f8a0f7be23261b4349eab33024b2007df0
GitHub commit

commit 657b745bebcd (kubeedge/kubeedge)

Fix landed in kubeedge/kubeedge commit 657b745bebcd — awaiting tagged release

https://github.com/kubeedge/kubeedge/commit/657b745bebcdd7a221eb34c0aac13231ef12c37f
GitHub commit

commit 552af457a4c7 (kubeedge/kubeedge)

Fix landed in kubeedge/kubeedge commit 552af457a4c7 — awaiting tagged release

https://github.com/kubeedge/kubeedge/commit/552af457a4c7ce80ea1678ab5889f475b36ea103
GitHub pull request

[release-1.21] Backport security hardening fixes for v1.21.2

Fix merged in kubeedge/kubeedge PR #7030 on 2026-07-15 — awaiting tagged release

https://github.com/kubeedge/kubeedge/pull/7030
GitHub pull request

[release-1.22] Backport security hardening fixes for v1.22.2

Fix merged in kubeedge/kubeedge PR #7029 on 2026-07-15 — awaiting tagged release

https://github.com/kubeedge/kubeedge/pull/7029
GitHub pull request

[release-1.23] Backport security hardening fixes for v1.23.1

Fix merged in kubeedge/kubeedge PR #7028 on 2026-07-15 — awaiting tagged release

https://github.com/kubeedge/kubeedge/pull/7028
GitHub advisoryMentions a patch (unverified)

Command Injection in NodeUpgradeJob - RCE on edge nodes via v1alpha2 API · Advisory · kubeedge/kubeedge · GitHub

https://github.com/kubeedge/kubeedge/security/advisories/GHSA-5jpj-293f-rhvj

Vendor Advisories for CVE-2026-62371(1)

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

Patch Availability(3)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
gogithub.com/kubeedge/kubeedge @ 1.21.2 (fixes >= 1.12.0, < 1.21.2)—ghsa
gogithub.com/kubeedge/kubeedge @ 1.22.2 (fixes >= 1.22.0, < 1.22.2)—ghsa
gogithub.com/kubeedge/kubeedge @ 1.23.1 (fixes >= 1.23.0, < 1.23.1)—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)
Go(1)
PackageVulnerable rangeFix by version rangeDependents
github.com/kubeedge/kubeedge—
  • 1.12.0 up to 1.21.2: fixed in 1.21.2
  • 1.22.0 up to 1.22.2: fixed in 1.22.2
  • 1.23.0 up to 1.23.1: fixed in 1.23.1
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 10× in last 7d / 49× 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:35 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  2. 2026-11-01 07:41 UTCEG score recompute
  3. 2026-11-01 07:41 UTCGHSA enrichmentGHSA-5jpj-293f-rhvj · GitHub severity HIGH · GitHub CVSS 8.8
  4. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  5. 2026-10-30 16:34 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  6. 2026-10-29 16:33 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  7. 2026-10-28 16:32 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  8. 2026-10-28 06:25 UTCEG score recompute
  9. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  10. 2026-10-26 16:32 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  11. 2026-10-25 16:33 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  12. 2026-10-25 14:14 UTCEG score recompute
  13. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  14. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  15. 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  16. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  17. 2026-10-20 18:53 UTCEG score recompute
  18. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  19. 2026-10-19 16:32 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  20. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  21. 2026-10-18 03:24 UTCEG score recompute
  22. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  23. 2026-10-16 16:43 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  24. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  25. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.5% · 40th percentile
Show 45 more
  1. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  2. 2026-10-13 12:54 UTCEG score recompute
  3. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  4. 2026-10-12 15:49 UTCEG score recompute
  5. 2026-10-11 19:34 UTCEG score recompute
  6. 2026-10-11 16:49 UTCEG score recompute
  7. 2026-10-11 14:11 UTCEG score recompute
  8. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  9. 2026-10-11 06:37 UTCEG score recompute
  10. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  11. 2026-10-09 20:56 UTCEG score recompute
  12. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  13. 2026-10-08 22:34 UTCEG score recompute
  14. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  15. 2026-10-07 23:58 UTCEG score recompute
  16. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  17. 2026-10-07 01:34 UTCEG score recompute
  18. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  19. 2026-10-06 03:11 UTCEG score recompute
  20. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  21. 2026-10-05 04:23 UTCEG score recompute
  22. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  23. 2026-10-03 18:48 UTCEG score recompute
  24. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  25. 2026-10-02 19:51 UTCEG score recompute
  26. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  27. 2026-10-01 21:32 UTCEG score recompute
  28. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  29. 2026-09-30 23:14 UTCEG score recompute
  30. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  31. 2026-09-30 00:53 UTCEG score recompute
  32. 2026-09-29 02:28 UTCEG score recompute
  33. 2026-09-28 15:19 UTCEG score recompute
  34. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  35. 2026-09-27 17:00 UTCEG score recompute
  36. 2026-09-26 18:43 UTCEG score recompute
  37. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  38. 2026-09-26 07:34 UTCEG score recompute
  39. 2026-09-24 14:23 UTCEG score recompute
  40. 2026-09-24 03:14 UTCEG score recompute
  41. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  42. 2026-09-22 17:46 UTCEG score recompute
  43. 2026-09-21 17:25 UTCEG score recompute
  44. 2026-09-21 17:10 UTCEG score recomputeFirst assessed: 8.8 HIGH
  45. 2026-09-21 17:10 UTCMITRE cvelistV5first tracked

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-62371?
CVE-2026-62371 is a high-severity vulnerability; its CVE record was published on September 21, 2026. KubeEdge is an open source system for extending native containerized application orchestration capabilities to hosts at Edge. From 1.12.0 until 1.21.2, 1.22.2, and 1.23.1, the v1alpha2 NodeUpgradeJob handler in edge/pkg/taskmanager/actions/nodeupgradejob.go concatenates authenticated…
When was the CVE record for CVE-2026-62371 published?
The CVE record for CVE-2026-62371 was published on September 21, 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 September 24, 2026; the record at its source may have been updated since.
Is CVE-2026-62371 actively exploited?
CVE-2026-62371 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (41st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-62371?
CVE-2026-62371 has a CVSS base score of 8.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-62371?
A fix for CVE-2026-62371 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-62371 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-62371

Explore →

Is Your Infrastructure Affected by CVE-2026-62371?

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

Book a Demo →Browse All CVEs