<?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-09T08:02:21.885342+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/euvd-2026-273579</id>
    <title>EUVD-2026-273579</title>
    <updated>2026-10-09T08:02:21.933865+00:00</updated>
    <content>EUVD-2026-273579</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-273579"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2026-24005</id>
    <title>fkie_cve-2026-24005</title>
    <updated>2026-10-09T08:02:21.933909+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Kruise provides automated management of large-scale applications on Kubernetes. Prior to versions 1.8.3 and 1.7.5, PodProbeMarker allows defining custom probes with TCPSocket or HTTPGet handlers. The webhook validation does not restrict the Host field in these probe configurations. Since kruise-daemon runs with hostNetwork=true, it executes probes from the node network namespace. An attacker with PodProbeMarker creation permission can specify arbitrary Host values to trigger SSRF from the node, perform port scanning, and receive response feedback through NodePodProbe status messages. Versions 1.8.3 and 1.7.5 patch the issue.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2026-24005"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-9fj4-3849-rv9g</id>
    <title>GHSA-9fj4-3849-rv9g — OpenKruise PodProbeMarker is Vulnerable to SSRF via Unrestricted Host Field</title>
    <updated>2026-10-09T08:02:21.933946+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Go: github.com/openkruise/kruise</p>
<p>## Summary</p>
<p>PodProbeMarker allows defining custom probes with TCPSocket or HTTPGet handlers. The webhook validation does not restrict the Host field in these probe configurations. Since kruise-daemon runs with hostNetwork=true, it executes probes from the node network namespace. An attacker with PodProbeMarker creation permission can specify arbitrary Host values (127.0.0.1, 169.254.169.254, internal IPs) to trigger SSRF from the node, perform port scanning, and receive response feedback through NodePodProbe status messages.</p>
<p>## Kubernetes Version</p>
<p>- Kubernetes: v1.30.0 (kind cluster)
- Distribution: kind</p>
<p>## Component Version</p>
<p>- OpenKruise: v1.8.0
- kruise-daemon: DaemonSet with hostNetwork=true
- Affected CRDs: PodProbeMarker, NodePodProbe</p>
<p>## Steps To Reproduce</p>
<p>### Environment Setup</p>
<p>1. Install OpenKruise v1.8.0 in kind cluster:
```bash
helm repo add openkruise https://openkruise.github.io/charts/
helm install kruise openkruise/kruise --version 1.8.0 \
  --namespace kruise-system --create-namespace
```</p>
<p>2. Verify kruise-daemon runs with hostNetwork:
```bash
kubectl -n kruise-system get ds kruise-daemon -o yaml | grep hostNetwork
```
Output:
```
hostNetwork: true
```</p>
<p>3. Create test namespace and RBAC:
```bash
kubectl apply -f - &lt;&lt;EOF
apiVersion: v1
kind: Namespace
metadata:
  name: tenant-a
---
apiVersion: v1
kind: ServiceAccount
metadata:
  name: attacker
  namespace: tenant-a
---
apiVersion: rbac.authorization.k8s.io/v1
kind: Role
metadata:
  name: ppm-creator
  namesp…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-9fj4-3849-rv9g"/>
  </entry>
</feed>
