<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Kiali – Security Bulletins</title>
    <link>https://v2-34.kiali.io/news/security-bulletins/</link>
    <description>Recent content in Security Bulletins on Kiali</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    
	  <atom:link href="https://v2-34.kiali.io/news/security-bulletins/index.xml" rel="self" type="application/rss+xml" />
    
    
      
        
      
    
    
    <item>
      <title>News: KIALI-SECURITY-004 - Missing namespace authorization checks in Kiali Server API endpoints</title>
      <link>https://v2-34.kiali.io/news/security-bulletins/kiali-security-004/</link>
      <pubDate>Mon, 02 Nov 2026 11:00:00 -0600</pubDate>
      
      <guid>https://v2-34.kiali.io/news/security-bulletins/kiali-security-004/</guid>
      <description>
        
        
        &lt;h2 id=&#34;description&#34;&gt;Description&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Disclosure date&lt;/strong&gt;: November 2, 2026&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Affected Releases&lt;/strong&gt;: Kiali Server 2.x releases prior to 2.34.1 (see per-finding details below)&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Impact Score&lt;/strong&gt;: &lt;a href=&#34;https://nvd.nist.gov/vuln-metrics/cvss/v3-calculator?vector=AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N&amp;amp;version=3.1&#34;&gt;4.3 - AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Several Kiali Server API endpoints returned data about namespaces the caller
had no RBAC access to (CWE-862, missing authorization). The impact is
confidentiality only: no secrets or traffic content were exposed and nothing
could be modified. The issues were reported to the Kiali security team by a
member of the community and were verified on Kiali Server 2.34.0.&lt;/p&gt;
&lt;p&gt;Kiali users are exposed to these findings depending on the endpoint:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Cluster health cache&lt;/strong&gt; — &lt;code&gt;GET /api/clusters/health?namespaces=&lt;/code&gt; served
cached health data for any namespace. The internal health cache is populated
by a background monitor running with Kiali&amp;rsquo;s ServiceAccount, and the handler
only RBAC-filtered the response when the namespaces parameter was empty.
This exposes application, service and workload names, replica counts, health
statuses and traffic rates. Affected releases: v2.22.0 and later (the health
cache is enabled by default since v2.22.0).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;ztunnel logs&lt;/strong&gt; — &lt;code&gt;GET /api/namespaces/{namespace}/pods/{pod}/logs?logType=ztunnel&lt;/code&gt;
streamed ztunnel access-log lines for any namespace. The ztunnel log path
fetches logs with Kiali&amp;rsquo;s ServiceAccount rather than the caller&amp;rsquo;s
credentials, so the API server never enforced RBAC. Additionally, the log
filter regexes were not anchored, so a pod name in the URL acted as a prefix
that could match workloads other than the one requested. This exposes pod,
workload and namespace names, SPIFFE identities, IP addresses and byte
counts. Requires an ambient mesh. Affected releases: v2.11.0 and later.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;ztunnel config dump&lt;/strong&gt; —
&lt;code&gt;GET /api/namespaces/{namespace}/pods/{pod}/config_dump_ztunnel&lt;/code&gt; returned
the full mesh-wide configuration dump — every workload, service and policy
in the mesh with pod IPs, service accounts and node information. The ztunnel
pod was located by name across the cluster, so the namespace in the URL was
irrelevant and no authorization check was performed. Requires an ambient
mesh. Affected releases: all 2.x releases.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Cluster-wide Istio config validations&lt;/strong&gt; —
&lt;code&gt;GET /api/istio/config?validate=true&lt;/code&gt; correctly filtered the returned Istio
config objects to the caller&amp;rsquo;s accessible namespaces, but the validation
entries attached to the response were not filtered. Any authenticated user
received validation entries (object kind, name, namespace, misconfiguration
messages and references to related objects) for Istio objects in every
namespace of the cluster. The namespace-scoped variant
(&lt;code&gt;GET /api/namespaces/{namespace}/istio?validate=true&lt;/code&gt;) is not affected.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;In addition, the &lt;code&gt;openshift&lt;/code&gt; authentication strategy accepted any token for
which user-info lookup succeeded, without checking that the user can view any
namespace — unlike the &lt;code&gt;openid&lt;/code&gt; strategy, which rejects such users. This
widened the audience of the findings above to any valid OpenShift token,
including ServiceAccounts that cannot see any namespace.&lt;/p&gt;
&lt;h2 id=&#34;mitigation&#34;&gt;Mitigation&lt;/h2&gt;
&lt;p&gt;If you can update:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Update to Kiali Server v2.34.1 or later. In addition to fixing the findings
above, this release makes namespace accessibility checks consistent across
all namespace-scoped API endpoints (including tracing endpoints, which
previously queried the tracing backend without a namespace check), and the
&lt;code&gt;openshift&lt;/code&gt; authentication strategy now rejects tokens that cannot view any
namespace.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;If you cannot update:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Disable the internal health cache by setting
&lt;code&gt;kiali_internal.health_cache.enabled: false&lt;/code&gt; in the Kiali CR to close the
cluster health exposure.&lt;/li&gt;
&lt;li&gt;Use the namespace-scoped Istio config validations endpoint
(&lt;code&gt;GET /api/namespaces/{namespace}/istio?validate=true&lt;/code&gt;) instead of the
cluster-wide one.&lt;/li&gt;
&lt;li&gt;There is no configuration-level mitigation for the ztunnel log and ztunnel
config dump endpoints. If you run an ambient mesh, restrict access to the
Kiali Server API (for example, via network policy) so that only trusted
users and workloads can reach it.&lt;/li&gt;
&lt;/ul&gt;

      </description>
    </item>
    
    <item>
      <title>News: KIALI-SECURITY-003 - Installation into ad-hoc namespaces</title>
      <link>https://v2-34.kiali.io/news/security-bulletins/kiali-security-003/</link>
      <pubDate>Tue, 11 May 2021 11:00:00 -0600</pubDate>
      
      <guid>https://v2-34.kiali.io/news/security-bulletins/kiali-security-003/</guid>
      <description>
        
        
        &lt;h2 id=&#34;description&#34;&gt;Description&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Disclosure date&lt;/strong&gt;: May 11, 2021&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Affected Releases&lt;/strong&gt;: prior to 1.33.0&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Impact Score&lt;/strong&gt;: &lt;a href=&#34;https://nvd.nist.gov/vuln-metrics/cvss/v3-calculator?vector=AV:N/AC:L/PR:H/UI:N/S:C/C:L/I:L/A:L&amp;amp;version=3.1&#34;&gt;6.6 - AV:N/AC:L/PR:H/UI:N/S:C/C:L/I:L/A:L&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;A vulnerability was found in the Kiali Operator allowing installation of a specified image into any namespace.&lt;/p&gt;
&lt;p&gt;Kiali users are exposed to this vulnerability if all the following conditions are met:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Kiali operator is used for installation.&lt;/li&gt;
&lt;li&gt;Kiali CR was edited to install an image into an unapproved namespace.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;This vulnerability is filed as
&lt;a href=&#34;https://access.redhat.com/security/cve/CVE-2021-3495&#34;&gt;CVE-2021-3495&lt;/a&gt;&lt;/p&gt;
&lt;h2 id=&#34;mitigation&#34;&gt;Mitigation&lt;/h2&gt;
&lt;p&gt;If you can update:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Update to Kiali Operator v1.33.0 or later.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;If you can not update:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Ensure only trusted individuals can create or edit a Kiali CRs (resources of kind &amp;ldquo;kiali&amp;rdquo;).&lt;/li&gt;
&lt;/ul&gt;

      </description>
    </item>
    
    <item>
      <title>News: KIALI-SECURITY-002 - Authentication bypass when using the OpenID login strategy</title>
      <link>https://v2-34.kiali.io/news/security-bulletins/kiali-security-002/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://v2-34.kiali.io/news/security-bulletins/kiali-security-002/</guid>
      <description>
        
        
        &lt;h2 id=&#34;description&#34;&gt;Description&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Disclosure date&lt;/strong&gt;: March 5, 2021&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Affected Releases&lt;/strong&gt;: 1.26.0, 1.26.1, 1.26.2, 1.27.0, 1.28.0, 1.28.1, 1.29.0, 1.29.1, 1.30.0&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Impact Score&lt;/strong&gt;: &lt;a href=&#34;https://nvd.nist.gov/vuln-metrics/cvss/v3-calculator?vector=AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N/E:F/RL:X/RC:C&amp;amp;version=3.1&#34;&gt;7.0 - AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N/E:F/RL:X/RC:C&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;A vulnerability was found in Kiali allowing an attacker to bypass the
authentication mechanism. The vulnerability lets an attacker build forged
credentials and use them to gain unauthorized access to Kiali.&lt;/p&gt;
&lt;p&gt;Kiali users are exposed to this vulnerability if all the following conditions are met:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Kiali is setup with the &lt;code&gt;openid&lt;/code&gt; authentication strategy.&lt;/li&gt;
&lt;li&gt;As a result of configurations in both Kiali and your OpenID server, Kiali uses the
&lt;em&gt;implicit flow&lt;/em&gt; of the OpenID specification to negotiate authentication.&lt;/li&gt;
&lt;li&gt;Kiali is setup with RBAC turned off.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;This vulnerability is filed as
&lt;a href=&#34;https://access.redhat.com/security/cve/CVE-2021-20278&#34;&gt;CVE-2021-20278&lt;/a&gt;&lt;/p&gt;
&lt;h2 id=&#34;mitigation&#34;&gt;Mitigation&lt;/h2&gt;
&lt;p&gt;If you can update:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Update to Kiali v1.31.0 or later.&lt;/li&gt;
&lt;li&gt;If you need an earlier version, only Kiali 1.26.3 and 1.29.2 are fixed.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;If you are locked with an older version of Kiali, you have three options:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Configure Kiali to use the &lt;em&gt;authorization code&lt;/em&gt; flow of the OpenID specification; or&lt;/li&gt;
&lt;li&gt;Configure Kiali to use the &lt;em&gt;implicit flow&lt;/em&gt; of the OpenID specification &lt;em&gt;and&lt;/em&gt; enable RBAC; or&lt;/li&gt;
&lt;li&gt;Configure Kiali to use any of the other available authentication mechanisms.&lt;/li&gt;
&lt;/ul&gt;

      </description>
    </item>
    
    <item>
      <title>News: KIALI-SECURITY-001 - Authentication bypass using forged credentials</title>
      <link>https://v2-34.kiali.io/news/security-bulletins/kiali-security-001/</link>
      <pubDate>Tue, 24 Mar 2020 11:00:00 -0600</pubDate>
      
      <guid>https://v2-34.kiali.io/news/security-bulletins/kiali-security-001/</guid>
      <description>
        
        
        &lt;h2 id=&#34;description&#34;&gt;Description&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Disclosure date&lt;/strong&gt;: March 25, 2020&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Affected Releases&lt;/strong&gt;: 0.4.0 to 1.15.0&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Impact Score&lt;/strong&gt;: &lt;a href=&#34;https://nvd.nist.gov/vuln-metrics/cvss/v3-calculator?vector=AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:H&amp;amp;version=3.1&#34;&gt;9.4 - AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:H&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;A vulnerability was found in Kiali allowing an attacker to bypass the
authentication mechanism. Currently, Kiali has four authentication mechanisms:
&lt;em&gt;login, token, openshift&lt;/em&gt; and &lt;em&gt;ldap&lt;/em&gt;. All are vulnerable.&lt;/p&gt;
&lt;p&gt;The vulnerability lets an attacker build forged credentials and use them to
gain unauthorized access to Kiali.&lt;/p&gt;
&lt;p&gt;Additionally, it was found that Kiali credentials were not being validated
properly. Depending on the authentication mechanism configured in Kiali, this
could facilitate unauthorized access into Kiali with forged and/or invalid
credentials.&lt;/p&gt;
&lt;p&gt;These vulnerabilities are filed as
&lt;a href=&#34;https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-1762&#34;&gt;CVE-2020-1762&lt;/a&gt;
and
&lt;a href=&#34;https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-1764&#34;&gt;CVE-2020-1764&lt;/a&gt;&lt;/p&gt;
&lt;h2 id=&#34;detection&#34;&gt;Detection&lt;/h2&gt;
&lt;p&gt;Use the following bash script to check if you are vulnerable:&lt;/p&gt;
&lt;pre tabindex=&#34;0&#34;&gt;&lt;code&gt;KIALI_VERSION=$(kubectl get pods -n istio-system -l app=kiali -o yaml | sed -n &amp;#39;s/^.*image: .*:v\(.*\)$/\1/p&amp;#39; | sort -u)
kubectl get deploy kiali -n istio-system -o yaml | grep -q LOGIN_TOKEN_SIGNING_KEY
TEST_KEY_ENV=$?
kubectl get cm kiali -n istio-system -o yaml | grep signing_key | grep -vq kiali
TEST_KEY_CFG=$?
VERSION_ENTRIES=(${KIALI_VERSION//./ })
echo &amp;#34;Your Kiali version found: ${KIALI_VERSION}&amp;#34;
[ ${VERSION_ENTRIES[0]} -lt &amp;#34;1&amp;#34; ] || ([ ${VERSION_ENTRIES[0]} -eq &amp;#34;1&amp;#34; ] &amp;amp;&amp;amp; (\
  [ ${VERSION_ENTRIES[1]} -lt &amp;#34;15&amp;#34; ] || ([ ${VERSION_ENTRIES[1]} -eq &amp;#34;15&amp;#34; ] &amp;amp;&amp;amp; ( \
  [ ${VERSION_ENTRIES[2]} -le &amp;#34;0&amp;#34; ])))) &amp;amp;&amp;amp; echo &amp;#34;Your Kiali version is vulnerable&amp;#34;
[ $TEST_KEY_ENV -eq 1 ] &amp;amp;&amp;amp; [ $TEST_KEY_CFG -eq 1 ] &amp;amp;&amp;amp; echo &amp;#34;Your Kiali configuration looks vulnerable&amp;#34;
&lt;/code&gt;&lt;/pre&gt;&lt;p&gt;The script output will be similar to this:&lt;/p&gt;
&lt;pre tabindex=&#34;0&#34;&gt;&lt;code&gt;Your Kiali version found: 1.14.0
Your Kiali version is vulnerable
Your Kiali configuration looks vulnerable
&lt;/code&gt;&lt;/pre&gt;&lt;h2 id=&#34;mitigation&#34;&gt;Mitigation&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Update to Kiali 1.15.1 or later.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Alternatively, if you cannot update to version 1.15.1, mitigation is possible by
&lt;a href=&#34;https://github.com/kiali/kiali/blob/a660a80b2add1fd2fcfb5662c63824ca1dff95b9/operator/deploy/kiali/kiali_cr.yaml#L602-L608&#34;&gt;setting a secure signing key&lt;/a&gt;
when deploying Kiali. If you installed via Kiali operator, you could use the following bash script:&lt;/p&gt;
&lt;pre tabindex=&#34;0&#34;&gt;&lt;code&gt;SIGN_KEY=$(chars=abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ1234567890; for i in {1..20}; do echo -n &amp;#34;${chars:RANDOM%${#chars}:1}&amp;#34;; done; echo)
kubectl get kiali -n $(kubectl get kiali --all-namespaces --no-headers -o custom-columns=NS:.metadata.namespace) -o yaml | sed &amp;#34;s/spec:/spec:\n    login_token:\n      signing_key: $SIGN_KEY/&amp;#34; | kubectl apply -f -
&lt;/code&gt;&lt;/pre&gt;&lt;p&gt;If you installed via Istio helm charts or &lt;code&gt;istioctl&lt;/code&gt; command, you could use the following bash script:&lt;/p&gt;
&lt;pre tabindex=&#34;0&#34;&gt;&lt;code&gt;KIALI_INSTALL_NAMESPACE=istio-system
SIGN_KEY=$(chars=abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ1234567890; for i in {1..20}; do echo -n &amp;#34;${chars:RANDOM%${#chars}:1}&amp;#34;; done; echo)
kubectl get cm kiali -n $KIALI_INSTALL_NAMESPACE -o yaml | sed &amp;#34;s/server:/login_token:\\n      signing_key: $SIGN_KEY\\n    server:/&amp;#34; | kubectl apply -f -
kubectl delete pod -l app=kiali -n $KIALI_INSTALL_NAMESPACE
&lt;/code&gt;&lt;/pre&gt;
      </description>
    </item>
    
  </channel>
</rss>
