<?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-09T01:14:53.812390+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-322626</id>
    <title>EUVD-2026-322626</title>
    <updated>2026-10-09T01:14:53.864585+00:00</updated>
    <content>EUVD-2026-322626</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-322626"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2026-45021</id>
    <title>fkie_cve-2026-45021</title>
    <updated>2026-10-09T01:14:53.864629+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Kuma is a modern Envoy-based service mesh that can run on every cloud across both Kubernetes and VMs. Prior to 2.7.25, 2.9.15, 2.11.13, 2.12.10, and 2.13.5, the default kuma-cp config leaks the admin bootstrap token and signing keys to any webpage the operator visits while the control plane is reachable from their browser. CorsAllowedDomains: [".*"] reflects any Origin, and LocalhostIsAdmin: true promotes requests from 127.0.0.1 to mesh-system:admin. A cross-origin fetch() from a malicious page returns the admin JWT and signing material. This vulnerability is fixed in 2.7.25, 2.9.15, 2.11.13, 2.12.10, and 2.13.5.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2026-45021"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-3vcp-chfh-f6r2</id>
    <title>GHSA-3vcp-chfh-f6r2 — Default kuma-cp leaks admin token cross-origin via CORS wildcard + LocalhostIsAdmin</title>
    <updated>2026-10-09T01:14:53.864696+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Go: github.com/kumahq/kuma</p>
<p>## Summary</p>
<p>Default `kuma-cp` config leaks the admin bootstrap token and signing keys to any webpage the operator visits while the control plane is reachable from their browser. `CorsAllowedDomains: [".*"]` reflects any `Origin`, and `LocalhostIsAdmin: true` promotes requests from `127.0.0.1` to `mesh-system:admin`. A cross-origin `fetch()` from a malicious page returns the admin JWT and signing material.</p>
<p>## Am I affected?</p>
<p>You are affected if all of these hold:</p>
<p>1. `kuma-cp` runs with default config (`CorsAllowedDomains: [".*"]` and `LocalhostIsAdmin: true`).
2. The control plane is reachable from a browser on the same machine:
   - `kuma-cp run` on a developer laptop
   - Docker `--network host` or port-publish on a workstation
   - `kubectl port-forward` from a machine that also browses the web
3. The operator visits a page running attacker JavaScript while the control plane is reachable.</p>
<p>You are not affected if:</p>
<p>- The control plane runs on a Kubernetes cluster accessed via ClusterIP, NodePort, or LoadBalancer from a remote client.
- The control plane runs on an SSH-administered VM with no browser on the host.
- `KUMA_API_SERVER_AUTHN_LOCALHOST_IS_ADMIN=false` is set (see https://kuma.io/docs/latest/production/secure-deployment/api-server-auth/).
- `KUMA_API_SERVER_CORS_ALLOWED_DOMAINS` is set to an explicit allowlist that excludes attacker origins.</p>
<p>## Mitigation</p>
<p>1. Set `KUMA_API_SERVER_AUTHN_LOCALHOST_IS_ADMIN=false` after retrieving the admin token.
2. Set `KUMA_AP…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-3vcp-chfh-f6r2"/>
  </entry>
</feed>
