CVE-2026-53954: Bugsink: DOS using large numbers of event tags
Summary In affected versions, Bugsink stores every tag supplied with an incoming event. An event with an unusually large number of custom (i.e. supplied by an attacker) tags can therefore make ingestion spend more time than intended writing tag rows. Bugsink uses a single-writer database architecture.
Published Jun 5, 2026 · Updated Jun 12, 2026
Affected packages
bugsink
- Ecosystem
- PyPI
- Affected
- <= 2.2.1
- Fixed in
- 2.2.2
- Check
pip show bugsink
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Summary
In affected versions, Bugsink stores every tag supplied with an incoming event. An event with an unusually large number of custom (i.e. supplied by an attacker) tags can therefore make ingestion spend more time than intended writing tag rows.
Bugsink uses a single-writer database architecture. That keeps the implementation simple, but it also means one expensive write transaction can delay other event digestion while it is running. In this case, it makes ingestion of other events wait until the transaction that writes the tags finishes, which effectively causes a temporary denial of service for other events.
Impact
Submitting such an event requires a valid project DSN. DSNs are sometimes visible in client-side applications, so they should not be treated as a strong security boundary, but the issue is still limited to ingestion for a Bugsink instance that accepts the event.
The impact is availability-only. The issue does not expose stored data, modify existing events, or allow code execution.
Mitigation
Update to version 2.2.2, which caps the number of tags stored for a single event. The default cap is 100 tags and can be changed with MAX_EVENT_TAGS.
Credited to seankohjs.
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 entriesCVE-2026-47715
Bugsink: Issue event views can show an event from another project if its UUID is known
low3.1Jun 5, 2026CVE-2026-47716
Bugsink: Issue bulk actions can affect another project’s issue if its UUID is known
low3.1Jun 5, 2026CVE-2026-47728
Bugsink: Project scoping missing in sourcemap and debug-file lookup
medium4.3Jun 5, 2026CVE-2026-44502
Bunsink has an SSRF bypass in `validate_webhook_url`
medium4.3May 8, 2026CVE-2026-40162
Bugsink affected by authenticated arbitrary file write in artifactbundle/assemble
high7.1Apr 10, 2026CVE-2026-27614
Bugsink is vulnerable to Stored XSS via Pygments fallback in stacktrace rendering
critical9.3Feb 25, 2026
