{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-82473 exists.","fix":"No fix has been published for CVE-2026-82473 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-82473 is a high-severity missing authorization vulnerability in kubeedge, published on 29 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-82473 and fix it if it is affected.\n\nWhat it is: CVE-2026-82473 is a high-severity missing authorization vulnerability in kubeedge, published on 29 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-82473 exists.\n\nAffected product: kubeedge. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-82473/ (Markdown: https://insights.sbomify.com/CVE-2026-82473/index.md)","id":"CVE-2026-82473","markdown":"https://insights.sbomify.com/CVE-2026-82473/index.md","name":"CVE-2026-82473","record":{"aliases":["GHSA-7v3q-r4cr-w389"],"analysis":{"component_type":"container_or_infrastructure","fix_type":"upgrade","impacts":["data_modify","denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"KubeEdge CloudCore","requires_auth":"none","summary":"Attackers can manipulate node upgrade status reports without authentication, deceiving the control plane and blocking upgrade scheduling.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[],"cvss":{"score":8.8,"severity":"high","source":"cna","vector":"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","version":"4.0"},"cwes":[{"id":"CWE-306","name":"Missing Authentication for Critical Functionality"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"KubeEdge CloudCore through 1.23.1 Missing Authentication on Node Task Endpoints","id":"CVE-2026-82473","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2026"},"n_packages":0,"n_references":5,"next":{"headline":"Sudo through 1.9.17p2 Intercept Policy Bypass via execveat","id":"CVE-2026-82474"},"packages":[],"prev":{"headline":"Documenso before 2.13.0 Unauthenticated File Upload via /api/files/upload-pdf","id":"CVE-2026-82472"},"products":["kubeedge"],"published":"2026-08-29","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-08-31","vendors":["kubeedge"]},"summary":"Attackers can manipulate node upgrade status reports without authentication, deceiving the control plane and blocking upgrade scheduling.","url":"https://insights.sbomify.com/CVE-2026-82473/"}