# Bugsink: DOS using large numbers of event tags

Advisory record · `GHSA-5x67-j5xg-c5gj`

- **Identifiers:** `GHSA-5x67-j5xg-c5gj` · `CVE-2026-53954` · `PYSEC-2026-2403`
- **State:** Confirmed
- **Severity:** CVSS 4.3 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-400](https://cwe.mitre.org/data/definitions/400.html)
- **Tags:** [Denial of service](https://agentprime.io/advisories/tag/dos.md)
- **Published:** 5 Jun 2026
- **Updated:** 13 Jul 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 5 Jun 2026, 21:45 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `bugsink` (PyPI): affected `<2.2.2`; fixed in `2.2.2`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Bugsink versions before 2.2.2 store every tag supplied with an incoming event, so an event carrying a very large number of attacker-supplied tags can slow ingestion. The single-writer database design means that slow write can block other events from being processed, causing a temporary denial of service. An attacker needs a valid project DSN, which may be visible in client-side applications, and the impact is limited to availability. Upgrade to Bugsink 2.2.2, which caps stored tags per event at 100 by default; this limit can be changed with MAX_EVENT_TAGS.

Written 6 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 4.3 Medium, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0056, the 47th percentile, on 15 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 15:02 UTC: First seen by agentprime
- 31 Oct 2026, 15:02 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-5x67-j5xg-c5gj)

## Sources

- [GitHub Advisory Database: GHSA-5x67-j5xg-c5gj](https://github.com/advisories/GHSA-5x67-j5xg-c5gj)
- [OSV: GHSA-5x67-j5xg-c5gj](https://osv.dev/vulnerability/GHSA-5x67-j5xg-c5gj)
- <https://github.com/bugsink/bugsink/security/advisories/GHSA-5x67-j5xg-c5gj>
- <https://github.com/bugsink/bugsink>
- <https://github.com/bugsink/bugsink/releases/tag/2.2.2>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-5x67-j5xg-c5gj>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-5x67-j5xg-c5gj/>. Everything for agents: <https://agentprime.io/llms.txt>.
