Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

Back
New CVE Detected

CVE-2026-82473 – Authentication Bypass / Task Status Spoofing – KubeEdge CloudCore ≤ 1.23.1

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-82473 is a missing-authentication vulnerability (CWE-306) in KubeEdge CloudCore through version 1.23.1. CloudCore’s HTTPS server accepts node task status reports — including node upgrade job status — without verifying the caller’s identity, allowing any network-reachable attacker to submit forged status reports. The issue is rated HIGH severity (8.8).

Technical details

  • Root cause: CloudCore’s HTTP(S) server processes node task status report requests without any authentication or authorization check.
  • Trigger condition: An attacker only needs network access to the CloudCore task-reporting endpoint on port 10002; no credentials or user interaction are required.
  • Attack vector: Network (AV:N), low attack complexity, no privileges or user interaction needed.
  • Impact: Attackers can submit crafted status reports to falsely mark node upgrade jobs as succeeded or failed, corrupting the control plane’s view of node upgrade state and disrupting/blocking scheduled node upgrades across the edge fleet.

Affected software

  • KubeEdge CloudCore, all versions through 1.23.1

Severity

  • CVSS v4.0: 8.8 (HIGH) — CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:L/SC:N/SI:N/SA:N
  • CVSS v3.1: 8.2 (HIGH) — CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:L

Mitigation and recommended actions

  • Immediate: No fixed release version has been publicly confirmed as of this writing; check the official KubeEdge GitHub Security Advisories page for an updated CloudCore release that adds authentication to the node task status reporting endpoint, and upgrade as soon as one is available.
  • If no patch is available: Restrict network access to CloudCore’s task-reporting service (port 10002) to trusted edge nodes and administrative networks only — do not expose it to the public internet. Use network segmentation, firewall rules, or a mutual-TLS/VPN boundary to limit reachability, and monitor for unsolicited or anomalous requests to the node-task status endpoint, correlating status changes against expected node-side upgrade logs and agent telemetry.

How IONIX identifies potentially affected assets

IONIX matches the following signals against data already collected when it crawled the asset; identifying the technology sends no request beyond that crawl.

  • TLS certificate: KubeEdge in the certificate subject organization, subject common name, issuer organization, and issuer common name fields.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge