CVE-2026-53954

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.

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.

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.

Crafted input forces the application to consume excessive CPU, memory, or other resources, degrading or denying service. Typical impact: denial of service.

CVE-2026-53954 has a CVSS score of 4.3 (Medium). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (2.2.2); upgrading removes the vulnerable code path.

Kodem intelligence

1. What is CVE-2026-53954? CVE-2026-53954 is a medium-severity uncontrolled resource consumption vulnerability in bugsink (pip), affecting versions <= 2.2.1. It is fixed in 2.2.2. Crafted input forces the application to consume excessive CPU, memory, or other resources, degrading or denying service.
2. How severe is CVE-2026-53954? CVE-2026-53954 has a CVSS score of 4.3 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of bugsink are affected by CVE-2026-53954? bugsink (pip) versions <= 2.2.1 is affected.
4. Is there a fix for CVE-2026-53954? Yes. CVE-2026-53954 is fixed in 2.2.2. Upgrade to this version or later.
5. Is CVE-2026-53954 exploitable, and should I be worried? Whether CVE-2026-53954 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
6. What actually determines whether CVE-2026-53954 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.
7. How do I fix CVE-2026-53954? Upgrade bugsink to 2.2.2 or later.