NewApp Monitoring is liveSign up free
AgentbeamBeta
Open-source package vulnerability · PyPI

CVE-2025-54433: Bugsink path traversal via event_id in ingestion

highCVSS 4.0 7.1GHSA-q78p-g86f-jg6q

Summary In affected versions, ingestion paths construct file locations directly from untrusted eventid input without validation. A specially crafted eventid 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.

Published Jul 29, 2025 · Updated Jul 30, 2025

Affected packages

bugsink

Ecosystem
PyPI
Affected
>= 1.7.0, < 1.7.4
Fixed in
1.7.4
Check
pip show bugsink

bugsink

Ecosystem
PyPI
Affected
>= 1.6.0, < 1.6.4
Fixed in
1.6.4
Check
pip show bugsink

bugsink

Ecosystem
PyPI
Affected
>= 1.5.0, < 1.5.5
Fixed in
1.5.5
Check
pip show bugsink

bugsink

Ecosystem
PyPI
Affected
< 1.4.3
Fixed in
1.4.3
Check
pip show bugsink

Advisory details

From the GitHub Advisory Database (CC BY 4.0).

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.

References

How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology

More PyPI vulnerabilities

All PyPI entries