{"id":"CVE-2025-54433","aliases":["GHSA-q78p-g86f-jg6q","PYSEC-2026-1226"],"title":"Bugsink path traversal via event_id in ingestion","summary":"Bugsink path traversal via event_id in ingestion","severity":"high","vendor":"bugsink","product":"bugsink","ecosystem":"pip","affected":["bugsink >= 1.7.0, < 1.7.4","bugsink >= 1.6.0, < 1.6.4","bugsink >= 1.5.0, < 1.5.5","bugsink < 1.4.3"],"patched":["bugsink 1.7.4","bugsink 1.6.4","bugsink 1.5.5","bugsink 1.4.3"],"published":"2025-07-29","updated":"2026-07-07","source":"OSV","sourceUrl":"https://osv.dev/vulnerability/GHSA-q78p-g86f-jg6q","references":[{"url":"https://github.com/bugsink/bugsink/security/advisories/GHSA-q78p-g86f-jg6q"},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-54433"},{"url":"https://github.com/bugsink/bugsink/commit/1001726f4389e982c486cdd5fa81941cb46cfc33"},{"url":"https://github.com/bugsink/bugsink/commit/211ddf76758c808c095b5f836c363f148d934d21"},{"url":"https://github.com/bugsink/bugsink/commit/2c41fbe3881bdea83399a7f9fdc8cff198ae089f"},{"url":"https://github.com/bugsink/bugsink/commit/53cf1a17a3e96f7c83c7451fd56f980a09d0c9b0"},{"url":"https://github.com/bugsink/bugsink/commit/55a155003d0b416ea008c5e7dcde85130ad21d9b"},{"url":"https://github.com/bugsink/bugsink/commit/b94aa8a5c96ce8cdd9711b6beb4e518264993ac2"},{"url":"https://github.com/bugsink/bugsink/commit/c341687bd655543730c812db35c29199f788be6b"},{"url":"https://github.com/bugsink/bugsink/commit/c87217bd565122ba70af90436e3ab2cd9bee658f"},{"url":"https://github.com/bugsink/bugsink"}],"tags":["osv","pip"],"epss":0.00555,"epssPercentile":0.43928,"ingestedAt":"2026-07-08T18:25:52.116Z","slug":"CVE-2025-54433","body":"## Overview\n\n## Summary\n\nIn 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.\n\nSubmitting 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.\n\n## Impact\n\nA 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.\n\nIf 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.\n\n## Mitigation\n\nUpdate 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.\n\n## Affected packages\n\n- `bugsink >= 1.7.0, < 1.7.4`\n- `bugsink >= 1.6.0, < 1.6.4`\n- `bugsink >= 1.5.0, < 1.5.5`\n- `bugsink < 1.4.3`\n\n## Remediation\n\nUpgrade to a patched release:\n\n- `bugsink 1.7.4`\n- `bugsink 1.6.4`\n- `bugsink 1.5.5`\n- `bugsink 1.4.3`","depth":"twilight","depthScore":41,"depthScoreParts":{"impact":41.3,"likelihood":0.1,"exploitation":0,"ransomware":0},"changes":[]}