bugsink
Affected
- introduced
1.7.0, fixed1.7.4(ecosystem)
Fixed versions
1.7.4
Fix
- Fixed version
1.7.4pip install --upgrade bugsink==1.7.4
Advisory
Also known as: CVE-2025-54433, PYSEC-2026-1226
Bugsink path traversal via event_id in ingestion
Summary
In affected versions, 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. While that limits exposure, DSNs are sometimes discoverable—for example, when included in frontend code—and should not be treated as a strong security boundary.
Impact
A valid DSN holder can craft an event_id that causes the ingestion process to write files outside its designated directory. This allows overwriting files accessible to the user running Bugsink.
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.
Mitigation
Update to version 1.7.4, 1.6.4, 1.5.5 or 1.4.3 , which require event_id to be a valid UUID and normalizes it before use in file paths.
High Basis: The source's own band: HIGH
1.7.0, fixed 1.7.4 (ecosystem)1.7.4
1.7.4pip install --upgrade bugsink==1.7.41.6.0, fixed 1.6.4 (ecosystem)1.6.4
1.6.4pip install --upgrade bugsink==1.6.41.5.0, fixed 1.5.5 (ecosystem)1.5.5
1.5.5pip install --upgrade bugsink==1.5.50, fixed 1.4.3 (ecosystem)1.4.3
1.4.3pip install --upgrade bugsink==1.4.3Fix 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