<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Istio on Insinuator.net - Bold Statements</title>
    <link>https://insinuator.net/tags/istio/</link>
    <description>Recent content in Istio on Insinuator.net - Bold Statements</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 20 May 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://insinuator.net/tags/istio/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>CVE-2026-47237 – Overly Permissive Istio Permissions Allow Kubeflow Authorization Token Stealing</title>
      <link>https://insinuator.net/2026/05/cve-2026-47237-overly-permissive-istio-permissions-allow-kubeflow-authorization-token-stealing/</link>
      <pubDate>Wed, 20 May 2026 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2026/05/cve-2026-47237-overly-permissive-istio-permissions-allow-kubeflow-authorization-token-stealing/</guid>
      <description>&lt;p&gt;Kubeflow is vulnerable to the theft of authorization tokens by any user of the&#xA;Kubeflow UI or APIs, such as the Dashboard, Pipelines API, or Notebooks. With&#xA;this token, the attacker can take over the user&amp;rsquo;s account and the data that is&#xA;processed by that user. The attacker needs a valid user with the &lt;code&gt;kubeflow-edit&lt;/code&gt;&#xA;or Contributor role in a random Kubeflow namespace to perform this attack. This&#xA;is given if &lt;em&gt;Automatic Profile Creation&lt;/em&gt; is enabled. A setup based on the&#xA;official manifests prior to version 1.10, and on most other packaged Kubeflow&#xA;distributions, is vulnerable.&lt;/p&gt;&#xA;&lt;p&gt;The Istio edit permissions were removed by Kubeflow in a timely manner. Affected&#xA;users should update to the latest version to mitigate this issue.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Security Considerations on Istio’s CRDs with Namespace-based Multi-Tenancy</title>
      <link>https://insinuator.net/2026/03/security-considerations-on-istios-crds-with-namespace-based-multi-tenancy/</link>
      <pubDate>Wed, 25 Mar 2026 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2026/03/security-considerations-on-istios-crds-with-namespace-based-multi-tenancy/</guid>
      <description>&lt;p&gt;We reported a possible Man-in-the-Middle (MitM) attack scenario in which&#xA;a &lt;code&gt;VirtualService&lt;/code&gt; can redirect or intercept traffic within the service mesh.&#xA;This affects Namespace-based Multi-Tenancy clusters where tenants have the&#xA;permissions to deploy Istio resources (&lt;code&gt;networking.istio.io/v1&lt;/code&gt;).&lt;/p&gt;&#xA;&lt;p&gt;In collaboration with Istio, we&#xA;published &lt;a href=&#34;https://istio.io/latest/blog/2026/security-considerations-on-namespace-based-multi-tenancy/&#34;&gt;a guest submission in Istio’s blog&lt;/a&gt; (as&#xA;well as below),&#xA;a &lt;a href=&#34;https://istio.io/latest/news/security/istio-security-2026-002/&#34;&gt;Security Bulletin&lt;/a&gt;,&#xA;and an update to&#xA;their &lt;a href=&#34;https://istio.io/latest/docs/ops/deployment/security-model/#k8s-account-compromise&#34;&gt;Security Model&lt;/a&gt; to&#xA;address this issue.&lt;/p&gt;&#xA;&lt;p&gt;This blog post highlights the risks of using Istio in multi-tenant clusters and&#xA;explains how users can mitigate these risks and safely operate Istio in their&#xA;deployments.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
