/

CVE-2026-82473

Severity:

HIGH RISK

(8.2)

Missing Authentication (CWE-306) in KubeEdge CloudCore

CVE-2026-82473

Deferred

Vulnerability type

Category:

Missing Authentication

CWE:

CWE-306

Impact:

Control-Plane Integrity Loss and Upgrade Scheduling Disruption

Severity:

HIGH RISK

(8.2)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

KubeEdge CloudCore accepts node task status reports over its HTTPS service without verifying that the sender is authorized. An attacker who can reach port 10002 may forge upgrade results, causing the control plane to record jobs as successful or failed and potentially disrupt further upgrade scheduling.

Affected context

The issue affects KubeEdge CloudCore deployments where the HTTPS server handling node task status reports is network-reachable and does not require authentication verification for those messages. Risk is greater when port 10002 is exposed beyond a tightly controlled management or cluster network, because unauthenticated parties may influence the control plane's view of node upgrade progress.

Exploit preconditions

  • Attack surface: CloudCore's HTTPS service on port 10002
  • Required access: Network connectivity to the task-status reporting endpoint; valid node credentials may not be required
  • Trigger point: Receipt and processing of a node upgrade task status report
  • Why exploitation is possible: The service accepts status information without adequately authenticating or authorizing the reporting node

Why this happens

The underlying flaw is an authentication and authorization gap in a control-plane message handler. Status reports that affect upgrade state are trusted based on receipt rather than being bound to an authenticated, authorized node identity. This behavior maps to CWE-306: Missing Authentication for Critical Function, because a security-sensitive operation can be invoked without confirming the identity of its caller.

Potential impact

  • An attacker may mark upgrade jobs as completed without the corresponding node operation
  • An attacker may mark upgrade jobs as failed and disrupt upgrade workflows
  • The control plane could make incorrect scheduling decisions
  • Administrators may receive misleading information about node upgrade status
  • Repeated forged reports could contribute to operational denial of service

General mitigation guidance

Mitigation generally focuses on authenticating and authorizing every control-plane status message that can change operational state.

Common defensive patterns include:

  • Requiring mutual authentication or equivalent strong identity verification for node reports
  • Binding reports to an authorized node identity and the specific task being reported
  • Rejecting unsigned, stale, duplicated, or structurally invalid status messages
  • Limiting port 10002 to trusted management and cluster networks through network policy or firewall controls
  • Applying least privilege to node and control-plane identities
  • Treating status reports as untrusted until validated against server-side task state

How teams detect issues like this

Organizations can look for this class of issue through:

  • Static analysis and code review checks for handlers that process state-changing messages without authentication middleware
  • Review of endpoint authorization requirements for control-plane and node-to-controller communication
  • Tests that submit status messages with missing, invalid, or mismatched identities and verify rejection
  • Network policy audits confirming that management service ports are not unnecessarily exposed
  • Monitoring for task-status reports from unknown nodes, unexpected network locations, duplicate submissions, or implausible state transitions
  • Automated security review tools that identify unauthenticated routes and sensitive operations lacking caller verification

Sources

SourceLink
github.comgithub.com/geo-chen/oss/blob/main/kubeedge.md
github.comgithub.com/kubeedge/kubeedge
github.comgithub.com/kubeedge/kubeedge/blob/v1.23.1/cloud/pkg/cloudhub/servers/httpserver/nodetask/report_status.go
github.comgithub.com/kubeedge/kubeedge/blob/v1.23.1/cloud/pkg/cloudhub/servers/httpserver/server.go
vulncheck.comvulncheck.com/advisories/kubeedge-cloudcore-through-1.23.1-missing-authentication-on-node-task-endpoints

Frequently asked

questions

It may be remotely exploitable when an attacker can reach CloudCore's task-status service on port 10002. Exploitability depends on network exposure and intervening access controls.

Not necessarily. The critical prerequisite is connectivity to the affected reporting endpoint and the ability to submit a message that the service accepts as a node status report.

Require strong authentication and authorization for every status report, validate the sender against the expected node and task, and reject messages that fail identity, freshness, or state-consistency checks.

Treat control-plane messages as untrusted input, enforce authenticated service-to-service communication, restrict management ports with network policy, and continuously test sensitive endpoints for missing authentication and authorization.

Find out what's already
exploitable in your codebase.