Upgrade disruption via unauthenticated task-status injection
Published Aug 29, 2026 · Updated Aug 29, 2026
Missing authentication in KubeEdge CloudCore through 1.23.1 allows remote attackers to forge node task status reports over HTTPS. The ReportStatus and UpgradeEdge handlers route attacker-supplied task events to the internal task manager without verifying a bearer token or client certificate. Network access to CloudCore port 10002 is sufficient to falsify upgrade state and block later upgrade scheduling.
Summary
What happened
Missing authentication in KubeEdge CloudCore through 1.23.1 allows remote attackers to forge node task status reports over HTTPS. The ReportStatus and UpgradeEdge handlers route attacker-supplied task events to the internal task manager without verifying a bearer token or client certificate. Network access to CloudCore port 10002 is sufficient to falsify upgrade state and block later upgrade scheduling.
The record
- CVE
- CVE-2026-82473
- Published
- Aug 29, 2026
- Updated
- Aug 29, 2026
- Vendor
- KubeEdge
- Product
- KubeEdge
- Classifications
- CWE-306, T1565.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 29, 2026CVE publishedPublication date reported by the CVE source.
- Aug 29, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=1.23.1
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Unauthenticated task-event injection PoCproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo