<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://vulnerability.circl.lu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-04T12:56:03.896210+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://vulnerability.circl.lu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/fkie_cve-2026-62371</id>
    <title>fkie_cve-2026-62371</title>
    <updated>2026-10-04T12:56:03.898280+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>KubeEdge is an open source system for extending native containerized application orchestration capabilities to hosts at Edge. From 1.12.0 until 1.21.2, 1.22.2, and 1.23.1, the v1alpha2 NodeUpgradeJob handler in edge/pkg/taskmanager/actions/nodeupgradejob.go concatenates authenticated user-controlled spec.version and spec.image values into the keadm upgrade edge shell command. A user with permission to create or update NodeUpgradeJob resources can supply shell metacharacters in either field, causing arbitrary commands to execute on targeted edge nodes with the privileges of the upgrade process and compromising node confidentiality, integrity, and availability. This issue is fixed in versions 1.21.2, 1.22.2, and 1.23.1.</p>
      </div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/fkie_cve-2026-62371"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/ghsa-5jpj-293f-rhvj</id>
    <title>GHSA-5jpj-293f-rhvj — KubeEdge: Command Injection in NodeUpgradeJob - RCE on edge nodes via v1alpha2 API</title>
    <updated>2026-10-04T12:56:03.898353+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Go: github.com/kubeedge/kubeedge</p>
<p>## Impact</p>
<p>The KubeEdge NodeUpgradeJob handler constructed the `keadm upgrade edge` command by concatenating the user-controlled `spec.version` and `spec.image` fields into a shell command.</p>
<p>An authenticated user with permission to create or update `NodeUpgradeJob` resources through the v1alpha2 API could include shell metacharacters in either field. When the upgrade job was processed, the injected command could be executed on the targeted edge node with the privileges available to the upgrade process.</p>
<p>Successful exploitation could result in arbitrary command execution and compromise the confidentiality, integrity, and availability of the affected edge node.</p>
<p>## Patches</p>
<p>The fix removes shell-based command construction and invokes `keadm` using a structured argument list through `exec.Command`.</p>
<p>The version and image values are passed as separate literal arguments and are no longer interpreted by a command shell.</p>
<p>The fixed versions:</p>
<p>* KubeEdge v1.23.1
* KubeEdge v1.22.2
* KubeEdge v1.21.2</p>
<p>## Workarounds</p>
<p>Until a patched version is available:</p>
<p>* restrict permission to create or update `NodeUpgradeJob` resources to trusted administrators;
* do not allow untrusted users or tenants to control the `spec.version` or `spec.image` fields;
* avoid using NodeUpgradeJob-based edge upgrades in environments where these fields may be influenced by untrusted users.</p>
<p>## Credits</p>
<p>KubeEdge thanks Sang-Hoon Choi ([KoreaSecurity](https://github.com/KoreaSecurity), Sejong University)
for res…</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/ghsa-5jpj-293f-rhvj"/>
  </entry>
</feed>
