GHSA-8HW4-FHWW-273G
Vulnerability from github – Published: 2026-04-10 19:30 – Updated: 2026-04-10 19:30Authenticated 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:
- modification of application data files
- corruption of uploaded assets or temporary files
- overwriting files in mounted writable volumes
- disruption of normal application behavior
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
- Affected: 2.1.0
- Fixed: 2.1.1
- Not affected: earlier releases
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.
{
"affected": [
{
"package": {
"ecosystem": "PyPI",
"name": "bugsink"
},
"ranges": [
{
"events": [
{
"introduced": "2.1.0"
},
{
"fixed": "2.1.1"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"2.1.0"
]
}
],
"aliases": [
"CVE-2026-40162"
],
"database_specific": {
"cwe_ids": [
"CWE-20"
],
"github_reviewed": true,
"github_reviewed_at": "2026-04-10T19:30:42Z",
"nvd_published_at": "2026-04-10T18:16:46Z",
"severity": "HIGH"
},
"details": "# Authenticated arbitrary file write in artifact bundle assembly\n\n## Summary\n\nAn authenticated file write vulnerability was identified in Bugsink **2.1.0** in the artifact bundle assembly flow.\n\nA user with a valid authentication token could cause the application to write attacker-controlled content to a filesystem location writable by the Bugsink process.\n\nThis issue requires authentication and affects only version **2.1.0**.\n\nThe issue is fixed in **2.1.1**.\n\n## Impact\n\nThis vulnerability allows an authenticated user to create or overwrite files **within locations writable by the Bugsink service account**.\n\nThe practical impact depends on the deployment environment and filesystem permissions of the running process.\n\nPossible consequences include:\n\n* modification of application data files\n* corruption of uploaded assets or temporary files\n* overwriting files in mounted writable volumes\n* disruption of normal application behavior\n\nNo unauthenticated exploitation is known.\n\nNo 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.\n\n## Affected versions\n\n* **Affected:** 2.1.0\n* **Fixed:** 2.1.1\n* **Not affected:** earlier releases\n\n## Mitigation\n\nUpgrade to **2.1.1**.\n\nAs a defense-in-depth measure, deployments should continue to ensure the Bugsink process runs with the **minimum required filesystem permissions**.",
"id": "GHSA-8hw4-fhww-273g",
"modified": "2026-04-10T19:30:42Z",
"published": "2026-04-10T19:30:42Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/bugsink/bugsink/security/advisories/GHSA-8hw4-fhww-273g"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-40162"
},
{
"type": "PACKAGE",
"url": "https://github.com/bugsink/bugsink"
},
{
"type": "WEB",
"url": "https://github.com/bugsink/bugsink/releases/tag/2.1.1"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:L",
"type": "CVSS_V3"
}
],
"summary": "Bugsink affected by authenticated arbitrary file write in artifactbundle/assemble"
}
Sightings
| Author | Source | Type | Date |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.