CVE-2026-82473
Received Received - Intake

KubeEdge CloudCore Unauthenticated Node Task Status Spoofing

Publication date: 2026-08-29

Last updated on: 2026-08-29

Assigner: VulnCheck

Description
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 Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-08-29
Last Modified
2026-08-29
Generated
2026-08-29
AI Q&A
2026-08-29
EPSS Evaluated
N/A
NVD
CVE-2026-82473
EUVD
EUVD-2026-68129

Affected Vendors & Products

Showing 3 associated CPEs
Vendor Product Version / Range
kubeedge cloudcore to 1.23.1 (inc)
kubeedge kubeedge to 1.23.1 (inc)
kubeedge kubeedge to 1.20.0 (inc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-306 The product does not perform any authentication for functionality that requires a provable user identity or consumes a significant amount of resources.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

CVE-2026-82473 is an unauthenticated task-event injection vulnerability in KubeEdge's CloudCore component. It affects HTTPS endpoints on port 10002 (/nodeupgrade and /task/{taskType}/name/{taskID}/node/{nodeID}/status) which accept requests without authentication. Attackers can manipulate upgrade jobs, mark tasks as failed, or inject arbitrary task-completion events, deceiving the control plane about node upgrade status.

Detection Guidance

Check if CloudCore is listening on port 10002 using netstat or ss. Test unauthenticated access to /nodeupgrade and /task/{taskType}/name/{taskID}/node/{nodeID}/status endpoints with curl. Monitor logs for unexpected task status reports or failed upgrade scheduling.

Impact Analysis

This vulnerability allows attackers to block upgrade scheduling by marking jobs as failed or succeeded without authentication. It can lead to incorrect node status reporting, disrupting cloud-edge collaboration and potentially causing system instability or failed deployments.

Compliance Impact

This vulnerability could impact compliance with GDPR and HIPAA by allowing unauthorized manipulation of node upgrade statuses. Attackers could deceive the control plane about node states, potentially leading to incorrect data processing or security configurations. This undermines integrity requirements in both regulations.

Mitigation Strategies

Upgrade KubeEdge to a patched version. Add authentication filters to nodetask routes or globally in the RESTful container. Restrict network access to port 10002 via firewall rules. Monitor for suspicious task status changes.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-82473. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart