Executive brief
Bugsink, an error-tracking and log aggregation tool, contains a vulnerability that allows logged-in users to write or overwrite files on the server. An attacker with valid credentials could use this to corrupt application data, modify uploaded assets, or disrupt the service's normal operations. This issue is limited to the specific permissions granted to the Bugsink service account on the host system.
Technical details
An authenticated arbitrary file write vulnerability exists in Bugsink version 2.1.0 within the 'artifactbundle/assemble' flow. The root cause is improper input validation (CWE-20) during the assembly of artifact bundles, which allows a user with a valid authentication token to specify filesystem locations for file writes. An attacker can create or overwrite any file that the Bugsink service account has write access to. While direct remote code execution has not been demonstrated, the impact includes data corruption and service disruption. The vulnerability is fixed in version 2.1.1.
Affected products
- bugsink bugsink 2.1.0
Timeline
- 2026-04-09: disclosed: Vulnerability published by the maintainer.
- 2026-04-10: advisory: GitHub Advisory and NVD entry published.
- 2026-04-10: patched: Version 2.1.1 released to address the issue.