<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>Governance on SILO</title>
    <link>https://silo.pgsty.com/tags/governance/</link>
    <description>Recent content in Governance on SILO</description>
    <generator>Hugo</generator>
    <language>en</language>
    
    
    
      <lastBuildDate>Sat, 24 Oct 2026 18:19:49 +0800</lastBuildDate>
    
    
      <atom:link href="https://silo.pgsty.com/tags/governance/index.xml" rel="self" type="application/rss+xml" />
    
    <item>
        <title>SN-2026-015 &amp; SN-2026-016: S3 Object Lock Governance Retention Bypass and Version-Addressed Overwrites</title>
        <link>https://silo.pgsty.com/blog/security/20260926-governance-retention-bypass/</link>
        <pubDate>Sat, 26 Sep 2026 00:00:00 +0000</pubDate>
        
        <guid>https://silo.pgsty.com/blog/security/20260926-governance-retention-bypass/</guid>
        <description>&lt;p&gt;&lt;strong&gt;&lt;code&gt;SN-2026-015&lt;/code&gt;&lt;/strong&gt; and &lt;strong&gt;&lt;code&gt;SN-2026-016&lt;/code&gt;&lt;/strong&gt; cover two S3 Object Lock retention and immutability vulnerabilities fixed in &lt;a href=&#34;https://silo.pgsty.com/blog/release/silo-20261018/&#34;&gt;SILO Server 20261018&lt;/a&gt; via PR &lt;a href=&#34;https://github.com/pgsty/silo/pull/234&#34;&gt;&lt;code&gt;#234&lt;/code&gt;&lt;/a&gt; (&lt;code&gt;14042b5aa&lt;/code&gt;) and PR &lt;a href=&#34;https://github.com/pgsty/silo/pull/235&#34;&gt;&lt;code&gt;#235&lt;/code&gt;&lt;/a&gt; (&lt;code&gt;0d3ba5d4c&lt;/code&gt;), as detailed in the companion &lt;a href=&#34;https://silo.pgsty.com/blog/design/governance-retention-bypass-repair/&#34;&gt;repair design note&lt;/a&gt;. While the delete path already enforced &lt;code&gt;s3:BypassGovernanceRetention&lt;/code&gt; (&lt;a href=&#34;https://github.com/minio/minio/security/advisories/GHSA-c8fc-mjj8-fc63&#34;&gt;CVE-2023-25812&lt;/a&gt;), the retention-write path (&lt;code&gt;PutObjectRetention&lt;/code&gt;) and four in-place version overwrite paths remained bypassable.&lt;/p&gt;&#xA;&lt;h2 id=&#34;advisory-scope-sn-2026-015-and-sn-2026-016&#34;&gt;Advisory Scope: &lt;code&gt;SN-2026-015&lt;/code&gt; and &lt;code&gt;SN-2026-016&lt;/code&gt;&#xA;&lt;/h2&gt;&#xA;&lt;h3 id=&#34;sn-2026-015&#34;&gt;SN-2026-015: &lt;code&gt;PutObjectRetention&lt;/code&gt; Authorization and Governance Bypass (&lt;code&gt;#231&lt;/code&gt;)&#xA;&lt;/h3&gt;&#xA;&lt;p&gt;In &lt;code&gt;PutObjectRetentionHandler&lt;/code&gt; (&lt;code&gt;cmd/object-handlers.go&lt;/code&gt;), three interacting flaws in &lt;code&gt;enforceRetentionBypassForPut&lt;/code&gt; and &lt;code&gt;isPutRetentionAllowed&lt;/code&gt; broke S3 Object Lock authorization:&lt;/p&gt;</description>
      </item>
    
  </channel>
</rss>
