<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://db.gcve.eu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Thu, 12 Nov 2026 04:37:12 +0000</lastBuildDate>
    <item>
      <title>PYSEC-2026-1494 — Kinto Attachment's attachments can be replaced on read-only records</title>
      <link>https://db.gcve.eu/vuln/pysec-2026-1494</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: kinto-attachment&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;The attachment file of an existing record can be replaced if the user has `&amp;#34;read&amp;#34;` permission on one of the parent (collection or bucket).&lt;/p&gt;
&lt;p&gt;And if the `&amp;#34;read&amp;#34;` permission is given to `&amp;#34;system.Everyone&amp;#34;` on one of the parent, then the attachment can be replaced on a record using an anonymous request.&lt;/p&gt;
&lt;p&gt;Note that if the parent has no explicit read permission, then the records attachments are safe.&lt;/p&gt;
&lt;p&gt;### Patches&lt;/p&gt;
&lt;p&gt;- Patch released in kinto-attachment 6.4.0
- https://github.com/Kinto/kinto-attachment/commit/f4a31484f5925cbc02b59ebd37554538ab826ca1&lt;/p&gt;
&lt;p&gt;### Workarounds&lt;/p&gt;
&lt;p&gt;None if the read permission has to remain granted.&lt;/p&gt;
&lt;p&gt;Updating to 6.4.0 or applying the patch individually (if updating is not feasible) is strongly recommended.&lt;/p&gt;
&lt;p&gt;### References&lt;/p&gt;
&lt;p&gt;- https://bugzilla.mozilla.org/show_bug.cgi?id=1879034&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: kinto-attachment&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;The attachment file of an existing record can be replaced if the user has `&amp;#34;read&amp;#34;` permission on one of the parent (collection or bucket).&lt;/p&gt;
&lt;p&gt;And if the `&amp;#34;read&amp;#34;` permission is given to `&amp;#34;system.Everyone&amp;#34;` on one of the parent, then the attachment can be replaced on a record using an anonymous request.&lt;/p&gt;
&lt;p&gt;Note that if the parent has no explicit read permission, then the records attachments are safe.&lt;/p&gt;
&lt;p&gt;### Patches&lt;/p&gt;
&lt;p&gt;- Patch released in kinto-attachment 6.4.0
- https://github.com/Kinto/kinto-attachment/commit/f4a31484f5925cbc02b59ebd37554538ab826ca1&lt;/p&gt;
&lt;p&gt;### Workarounds&lt;/p&gt;
&lt;p&gt;None if the read permission has to remain granted.&lt;/p&gt;
&lt;p&gt;Updating to 6.4.0 or applying the patch individually (if updating is not feasible) is strongly recommended.&lt;/p&gt;
&lt;p&gt;### References&lt;/p&gt;
&lt;p&gt;- https://bugzilla.mozilla.org/show_bug.cgi?id=1879034&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/pysec-2026-1494</guid>
    </item>
  </channel>
</rss>
