CVE-2026-62371

HIGHPre-NVD 8.88.8—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.8 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.9%, top 42% 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, secondary
Trending — 3 sources updated this week
8.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 8.8Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.8(medium)
EG Risk
44(Track)
EG Risk 44/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
Severity88% × 45%
Exploitation1% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
58%
KEV
Not listed

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.
generic

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

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

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

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

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_pr

[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_pr

[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_pr

[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 Patch Available

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.

Affected Packages

(1 across 1 ecosystem)
Go(1)
PackageVulnerable rangeFixed inDependents
github.com/kubeedge/kubeedge—1.21.2—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 7× in last 7d / 7× 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-09-24 14:23 UTCEG score recompute
  2. 2026-09-24 03:14 UTCEG score recompute
  3. 2026-09-23 17:54 UTCEPSS rescore
  4. 2026-09-22 17:46 UTCEG score recompute
  5. 2026-09-21 17:25 UTCEG score recompute
  6. 2026-09-21 17:10 UTCEG score recompute
  7. 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 vulnerability 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 CVE-2026-62371 disclosed?
CVE-2026-62371 was first published in the National Vulnerability Database on September 21, 2026, with the most recent update on September 24, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-62371 actively exploited?
CVE-2026-62371 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 42.4% of all scored CVEs.
What is the CVSS score of CVE-2026-62371?
CVE-2026-62371 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-62371?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-62371, 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

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