Vulnerability · Published Sep 15, 2026 · Assigned by GitHub_M

CVE-2026-53954Bugsink: DOS using large numbers of event tags

Medium 4.3

In plain English

A medium-severity uncontrolled resource consumption in bugsink from bugsink. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.6% (higher than 47% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.

Severity (CVSS 3.1)4.3Medium
Exploit odds (30 days)0.6%top 53.2% of all CVEs
Exploited in the wildNo reportsCISA SSVC: none
Attack toolingNoneno public tooling known

Official description

Bugsink is a self-hosted error tracking tool. Prior to version 2.2.2, Bugsink stores every set of custom tags supplied with an incoming event, allowing a caller with a valid project DSN to submit an unusually large tag set and force excessive tag-row writes. Because Bugsink uses a single-writer database architecture, the expensive write transaction delays digestion of other events and causes a temporary ingestion denial of service. Version 2.2.2 applies the configurable MAX_EVENT_TAGS limit before storage. The impact is limited to availability for an instance accepting the event and does not expose stored data, modify existing events, or allow code execution. This issue is fixed in version 2.2.2.

Affected packages & fixed versions

EcosystemPackageFixed inAdvisory
PyPIbugsink2.2.2GHSA-5x67-j5xg-c5gj
PyPIbugsink2.2.2PYSEC-2026-2403

Affected products (as reported)

VendorProductVersions
bugsink bugsink < 2.2.2

Weakness: CWE-400 · Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L

References