bugsink
Affected
- introduced
2.1.0, fixed2.1.1(ecosystem)
Fixed versions
2.1.1
Fix
- Fixed version
2.1.1pip install --upgrade bugsink==2.1.1
Advisory
Also known as: CVE-2026-40162, PYSEC-2026-2404
Bugsink affected by authenticated arbitrary file write in artifactbundle/assemble
Authenticated arbitrary file write in artifact bundle assembly
Summary
An authenticated file write vulnerability was identified in Bugsink 2.1.0 in the artifact bundle assembly flow.
A user with a valid authentication token could cause the application to write attacker-controlled content to a filesystem location writable by the Bugsink process.
This issue requires authentication and affects only version 2.1.0.
The issue is fixed in 2.1.1.
Impact
This vulnerability allows an authenticated user to create or overwrite files within locations writable by the Bugsink service account.
The practical impact depends on the deployment environment and filesystem permissions of the running process.
Possible consequences include:
No unauthenticated exploitation is known.
No direct code execution has been demonstrated as part of this issue, though impact may be greater in deployments where the process has broad write permissions.
Affected versions
Mitigation
Upgrade to 2.1.1.
As a defense-in-depth measure, deployments should continue to ensure the Bugsink process runs with the minimum required filesystem permissions.
High Basis: The source's own band: HIGH
2.1.0, fixed 2.1.1 (ecosystem)2.1.1
2.1.1pip install --upgrade bugsink==2.1.1Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0