<?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://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-15T22:32:51.264850+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" 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://cve.radiocsirt.org/vuln/cve-2025-59376</id>
    <title>CVE-2025-59376</title>
    <updated>2026-10-15T22:32:51.298176+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> feiskyer mcp-kubernetes-server</p>
<p>feiskyer mcp-kubernetes-server through 0.1.11 does not consider chained commands in the implementation of --disable-write and --disable-delete, e.g., it allows a "kubectl version; kubectl delete pod" command because the first word (i.e., "version") is not a write or delete operation.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/cve-2025-59376"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/pysec-2026-1619</id>
    <title>PYSEC-2026-1619 — mcp-kubernetes-server has a Command Injection vulnerability</title>
    <updated>2026-10-15T22:32:51.298230+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> PyPI: mcp-kubernetes-server</p>
<p>`mcp-kubernetes-server` does not correctly enforce the `--disable-write` / `--disable-delete` protections when commands are chained. The server only inspects the first token to decide whether an operation is write/delete, which allows a read-like command to be followed by a write action using shell metacharacters (e.g., `kubectl version; kubectl delete pod &lt;name&gt;`). A remote attacker who can invoke the server may therefore bypass the intended write/delete restrictions and perform state-changing operations against the Kubernetes cluster.</p>
<p>**Affected versions:** through `0.1.11` (no patched release available as of now).</p>
<p>**Mitigations:**
- Run with `--disable-kubectl` and/or `--disable-helm` to fully block those execution paths.
- Put the server behind an allow-list proxy restricting allowed subcommands.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/pysec-2026-1619"/>
  </entry>
</feed>
