<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Go on Kuldeep Pisda</title><link>https://kdpisda.in/tag/go/</link><description>Recent content in Go on Kuldeep Pisda</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 02 Nov 2026 08:30:00 +0530</lastBuildDate><atom:link href="https://kdpisda.in/tag/go/index.xml" rel="self" type="application/rss+xml"/><item><title>LXD and Incus Checked Every Certificate in the Client's Chain Against the Trust Store. Only the First One Proves a Key</title><link>https://kdpisda.in/lxd-mtls-client-certificate-chain-cve-2026-112816/</link><pubDate>Mon, 02 Nov 2026 08:30:00 +0530</pubDate><guid>https://kdpisda.in/lxd-mtls-client-certificate-chain-cve-2026-112816/</guid><description>&lt;p&gt;LXD&amp;rsquo;s remote API authenticated clients with mutual TLS and a trust store of pinned client certificates. The server took the certificate chain a client presented, compared every certificate in it against the trust store, and accepted the client if any of them matched. &lt;a href="https://discourse.ubuntu.com/t/security-advisory-critical-vulnerability-found-in-canonical-lxd-and-microcloud/90557"&gt;Canonical&amp;rsquo;s advisory&lt;/a&gt; describes the consequence: only the leaf certificate proves possession of a private key, so an attacker can put a trusted client&amp;rsquo;s public certificate behind their own and be treated as that client. The CVE is CVE-2026-112816 and it is scored 10.0.&lt;/p&gt;</description></item></channel></rss>