CVE-2026-82473

HIGHPre-NVD 8.28.2—
EchelonGraph scoreHIGH confidence

Score 8.2 from GitHub Security Advisory (severity: HIGH) published 2026-08-29. a secondary CVSS source baseline 8.2; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: ghsa, secondary
Trending — 3 sources updated this week
8.2EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: —CVSS: 8.2Exploit: None knownExposed: 0

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

KubeEdge CloudCore through 1.23.1 accepts node task status reports on its HTTPS server without authentication verification. Attackers can reach CloudCore on port 10002 to mark upgrade jobs as succeeded or failed, deceiving the control plane about node upgrade status and blocking further upgrade scheduling.

CVSS v3
8.2
EG Score
8.2(high)
EG Risk
41(Track)
EG Risk 41/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
Severity82% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
—
EPSS %ILE
—
KEV
Not listed

Published

August 29, 2026

Last Modified

August 29, 2026

Advisory Details (5)

Auto-updated Aug 29, 2026
No patch confirmed yet.
generic

KubeEdge CloudCore through 1.23.1 Missing Authentication on Node Task Endpoints | Advisories | VulnCheck

https://www.vulncheck.com/advisories/kubeedge-cloudcore-through-1.23.1-missing-authentication-on-node-task-endpoints
generic

GitHub - kubeedge/kubeedge: Kubernetes Native Edge Computing Framework (project under CNCF) · GitHub

https://github.com/kubeedge/kubeedge
generic

kubeedge/cloud/pkg/cloudhub/servers/httpserver/nodetask/report_status.go at v1.23.1 · kubeedge/kubeedge · GitHub

https://github.com/kubeedge/kubeedge/blob/v1.23.1/cloud/pkg/cloudhub/servers/httpserver/nodetask/report_status.go
generic

kubeedge/cloud/pkg/cloudhub/servers/httpserver/server.go at v1.23.1 · kubeedge/kubeedge · GitHub

https://github.com/kubeedge/kubeedge/blob/v1.23.1/cloud/pkg/cloudhub/servers/httpserver/server.go
generic

oss/kubeedge.md at main · geo-chen/oss · GitHub

https://github.com/geo-chen/oss/blob/main/kubeedge.md

Vendor Advisories for CVE-2026-82473(1)

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

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 5× in last 7d / 5× 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-08-30 04:46 UTCEG score recompute
  2. 2026-08-30 04:46 UTCGHSA enrichment
  3. 2026-08-29 17:28 UTCEG score recompute
  4. 2026-08-29 16:41 UTCEG score recompute
  5. 2026-08-29 16:37 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(4)

What is CVE-2026-82473?
CVE-2026-82473 is a high vulnerability published on August 29, 2026. KubeEdge CloudCore through 1.23.1 accepts node task status reports on its HTTPS server without authentication verification. Attackers can reach CloudCore on port 10002 to mark upgrade jobs as succeeded or failed, deceiving the control plane about node upgrade status and blocking further upgrade…
When was CVE-2026-82473 disclosed?
CVE-2026-82473 was first published in the National Vulnerability Database on August 29, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
What is the CVSS score of CVE-2026-82473?
CVE-2026-82473 has a CVSS v3 base score of 8.2 (NVD).
How do I remediate CVE-2026-82473?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-82473, 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-2026-82473

Explore →

Is Your Infrastructure Affected by CVE-2026-82473?

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

Start Free Scan →Browse All CVEs