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

CVE-2025-54433 · Severity: medium · CVSS 4 · Published 2026-07-07

Bugsink path traversal via event_id in ingestion

Technologies: bugsink (PyPI). Vendors: PyPI.

Quick answers

Is CVE-2025-54433 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2025-54433 being exploited in the wild.
How severe is CVE-2025-54433?
Medium severity, with a CVSS score of 4, published 7 July 2026.
Which products and versions are affected?
bugsink (PyPI) ECOSYSTEM:introduced=0,fixed=1.4.3,introduced=1.5.0,fixed=1.5.5,introduced=1.6.0,fixed=1.6.4,introduced=1.7.0,fixed=1.7.4,introduced=1.6.0,fixed=1.6.4, ECOSYSTEM:introduced=1.7.0,fixed=1.7.4.
Is there a fix for CVE-2025-54433?
Yes. bugsink (PyPI): upgrade to 1.6.4, 1.7.4 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2025-54433?
Check whether you run bugsink (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • bugsink (PyPI): upgrade to 1.6.4, 1.7.4 or later
    pip install "bugsink>=1.7.4"

Affected products

  • bugsink (PyPI) ECOSYSTEM:introduced=0,fixed=1.4.3,introduced=1.5.0,fixed=1.5.5,introduced=1.6.0,fixed=1.6.4,introduced=1.7.0,fixed=1.7.4,introduced=1.6.0,fixed=1.6.4, ECOSYSTEM:introduced=1.7.0,fixed=1.7.4

Identifiers

  • CVE-2025-54433
  • GHSA-q78p-g86f-jg6q
  • PYSEC-2026-1226

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.