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.
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.
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.
Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files. Typical impact: unauthorized file read or write outside the intended directory.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Remediation advice
bugsink to 1.7.4 or later; bugsink to 1.6.4 or later; bugsink to 1.5.5 or later; bugsink to 1.4.3 or later
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is CVE-2025-54433? CVE-2025-54433 is a high-severity path traversal vulnerability in bugsink (pip), affecting versions >= 1.7.0, < 1.7.4. It is fixed in 1.7.4, 1.6.4, 1.5.5, 1.4.3. Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files.
- Which versions of bugsink are affected by CVE-2025-54433? bugsink (pip) versions >= 1.7.0, < 1.7.4 is affected.
- Is there a fix for CVE-2025-54433? Yes. CVE-2025-54433 is fixed in 1.7.4, 1.6.4, 1.5.5, 1.4.3. Upgrade to this version or later.
- Is CVE-2025-54433 exploitable, and should I be worried? Whether CVE-2025-54433 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2025-54433 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2025-54433?
- Upgrade
bugsinkto 1.7.4 or later - Upgrade
bugsinkto 1.6.4 or later - Upgrade
bugsinkto 1.5.5 or later - Upgrade
bugsinkto 1.4.3 or later
- Upgrade