CVE-2026-40162: Bugsink 2.1.0 Authenticated Arbitrary File Write Vulnerability
Summary
CVE-2026-40162: Bugsink affected by authenticated arbitrary file write in artifactbundle/assemble. Affects bugsink versions >= 2.1.0, < 2.1.1. Fixed in 2.1.1. How to fix ↓
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Background
Bugsink is an open-source application designed for managing and assembling artifact bundles. It allows users to upload, modify, and manage files within a structured environment. The application is built to facilitate collaboration and streamline workflows, but it is susceptible to specific vulnerabilities that can compromise its integrity and security.
Vulnerability Detail
An authenticated arbitrary file write vulnerability was discovered in Bugsink version 2.1.0. This flaw allows a user with a valid authentication token to write attacker-controlled content to any filesystem location that is writable by the Bugsink process. The implications of this vulnerability can vary based on the deployment environment and the filesystem permissions granted to the Bugsink service account. Potential consequences include modification of application data files, corruption of uploaded assets, overwriting files in mounted writable volumes, and disruption of normal application behavior. No unauthenticated exploitation has been reported, and while direct code execution has not been demonstrated, the risk increases in environments with broad write permissions.
How To Fix
Latest published version: 2.6.2 as of 23 Oct 2026
pip install --upgrade "bugsink==2.6.2"Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.
If you need the minimum change
2.1.1
This is the first release that contains the fix.
pip install --upgrade "bugsink==2.1.1"Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →
Workaround
As a defense-in-depth measure, ensure that the Bugsink process operates with the minimum required filesystem permissions to limit the impact of potential exploitation.
Conclusion
The authenticated arbitrary file write vulnerability in Bugsink version 2.1.0 poses significant risks to applications using this version. It is crucial to upgrade to version 2.1.1 to mitigate these risks. Additionally, employing best practices regarding filesystem permissions can further enhance security.
See every vulnerability recorded for bugsink →
FAQ
The CVSS score for this vulnerability is 7.1, indicating a high severity level.
Only Bugsink version 2.1.0 is affected by this vulnerability. Versions prior to 2.1.0 and version 2.1.1 and later are not affected.
You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.
The impacts include unauthorized modification of application data, corruption of files, and disruption of application behavior, depending on filesystem permissions.
Yes, you can limit the filesystem permissions of the Bugsink process to reduce the potential impact of this vulnerability until you can upgrade.
Related vulnerabilities
Recent vulnerabilities recorded for bugsink.
