https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Thu, 15 Oct 2026 19:31:25 +0000 https://cve.radiocsirt.org/vuln/euvd-2026-252634 EUVD-2026-252634 https://cve.radiocsirt.org/vuln/euvd-2026-252634 https://cve.radiocsirt.org/vuln/fkie_cve-2025-59376 <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 &#34;kubectl version; kubectl delete pod&#34; command because the first word (i.e., &#34;version&#34;) is not a write or delete operation.</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 &#34;kubectl version; kubectl delete pod&#34; command because the first word (i.e., &#34;version&#34;) is not a write or delete operation.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2025-59376 https://cve.radiocsirt.org/vuln/ghsa-hjm5-xgj8-vwj6 <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> <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> https://cve.radiocsirt.org/vuln/ghsa-hjm5-xgj8-vwj6 https://cve.radiocsirt.org/vuln/pysec-2026-1619 <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> <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> https://cve.radiocsirt.org/vuln/pysec-2026-1619