PyPI: kinto-attachment

CVE-2024-1314

Safety vulnerability ID: SFTY-20240315-02837

Safety legacy ID: pyup.io-66714

kinto-attachment versions above 6.4.0 are susceptible to a vulnerability where an attachment file on an existing record can be replaced by users who possess "read" permission on any of the parent entities, such as a collection or bucket. Should this "read" permission be granted to "system.Everyone" on one of the parents, it enables the replacement of an attachment on a record through an anonymous request. Importantly, should the parent entities not have explicit "read" permission assigned, the attachments on records remain secure against such unauthorized replacements.

Created at: Nov 6, 2025Updated at: Nov 6, 2025

Overview

Kinto Attachment's attachments can be replaced on read-only records

Advisory

kinto-attachment versions above 6.4.0 are susceptible to a vulnerability where an attachment file on an existing record can be replaced by users who possess "read" permission on any of the parent entities, such as a collection or bucket. Should this "read" permission be granted to "system.Everyone" on one of the parents, it enables the replacement of an attachment on a record through an anonymous request. Importantly, should the parent entities not have explicit "read" permission assigned, the attachments on records remain secure against such unauthorized replacements.

Affected Package

Affecting kinto-attachment package, versions<6.4.0

Also affects

---

How to Fix

Upgradekinto-attachmentto6.4.0or higher.

Mitigation and Workarounds

---

Vulnerable Functions

Functions linked to known vulnerabilities.

Vulnerable function data is available for Enterprise customers

Book a call with us to see Safety in action.

Safety

Verified by Safety

Our Cybersecurity Intelligence Team reviewed this vulnerability. We combine public data with our own research to find issues not yet reported to public sources.

Learn more