<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Dependency on SILO</title><link>https://silo.pgsty.com/tags/dependency/</link><description>Recent content in Dependency on SILO</description><generator>Hugo</generator><language>en</language><lastBuildDate>Sun, 02 Aug 2026 15:22:46 +0800</lastBuildDate><atom:link href="https://silo.pgsty.com/tags/dependency/index.xml" rel="self" type="application/rss+xml"/><item><title>CVE-2026-32285: The jsonparser Advisory That Required No Patch</title><link>https://silo.pgsty.com/blog/security/cve-2026-32285/</link><pubDate>Wed, 15 Apr 2026 00:00:00 +0000</pubDate><guid>https://silo.pgsty.com/blog/security/cve-2026-32285/</guid><description>&lt;p&gt;&lt;strong&gt;Status:&lt;/strong&gt; Closed without a code change&lt;br&gt;
&lt;strong&gt;GitHub issue:&lt;/strong&gt; &lt;a href="https://github.com/pgsty/minio/issues/26"&gt;pgsty/minio#26&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Security maintenance is not always a sequence of “find a vulnerability, then ship a patch.” The initial assessment of CVE-2026-32285 was that the repository might still carry a vulnerable &lt;code&gt;jsonparser&lt;/code&gt;; replacing the dependency or maintaining another fork was even considered. Checking the resolved module version and actual reachability changed the conclusion: the tree already used &lt;code&gt;v1.1.2&lt;/code&gt;, which contained the fix, and &lt;code&gt;govulncheck&lt;/code&gt; found no reachable vulnerable symbol.&lt;/p&gt;</description></item></channel></rss>