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.
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
| Score | Rating | CVSS | Vector | Source |
|---|---|---|---|---|
| 4.3 | Medium | 3.1 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L | 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