CVE-2026-53954— Bugsink: DOS using large numbers of event tags
Quick assessment
Affected
bugsink bugsink
Exploitation
No confirmed in-the-wild exploitation; assess based on exposure
Recommended action
Check the vendor advisory and references for a fixed version. If immediate upgrade is impossible, restrict exposure and increase monitoring.
Bugsink 是一款自托管的错误跟踪工具。在 2.2.2 版本之前，Bugsink 会保存随每个传入事件提交的所有自定义标签集合。这意味着，拥有有效项目 DSN 的调用者可以提交异常大量的标签集，从而强制系统执行过度的标签行写入操作。由于 Bugsink 采用单写入者数据库架构，这种高耗时的写入事务会延迟对其他事件的消化处理，导致短暂的摄取（ingestion）拒绝服务（Denial of Service）。 2.2.2 版本在存储前应用了可配置的 MAX_EVENT_TAGS 限制。该漏洞的影响仅限于接受该事件
Possible ATT&CK Techniques 2 AI
T1499 · Endpoint Denial of Service T1082 · System Information Discovery
Get alerts for future matching vulnerabilities
Log in to subscribe
I. Basic Information for CVE-2026-53954
Vulnerability Information
Have questions about the vulnerability? See if Shenlong's analysis helps!
View Shenlong Deep Dive ↗
Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.
Vulnerability Title
Bugsink: DOS using large numbers of event tags
Source: CVE Program / CVE List V5
Vulnerability 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.
Source: CVE Program / CVE List V5
CVSS Information
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L
Source: CVE Program / CVE List V5
Vulnerability Type
未加控制的资源消耗(资源穷尽)
Source: CVE Program / CVE List V5
Affected Products
II. Public POCs for CVE-2026-53954
| # | POC Description | Source Link | Shenlong Link |
|---|
AI-Generated POC
Premium
No public POC found.
Login to generate AI POCIII. Intelligence Information for CVE-2026-53954
请登录查看更多情报信息。
Vendor Advisories for CVE-2026-53954 (1)
-
🔗 DOS using large numbers of event tags · Advisory · bugsink/bugsink · GitHub x_refsource_CONFIRM
Vendor Pages for CVE-2026-53954 (1)
-
🔗 Release 2.2.2 · bugsink/bugsink · GitHub x_refsource_MISC
IV. Related Vulnerabilities
Same product: bugsink
-
CVE-2026-47716
Bugsink: Issue bulk actions can affect another project’s iss -
CVE-2026-47715
Bugsink: Issue event views can show an event from another pr -
CVE-2026-47728
Bugsink: Project scoping missing in sourcemap and debug-file -
CVE-2026-44502
Bugsink: SSRF bypass in `validate_webhook_url` -
CVE-2026-40162
Bugsink affected by authenticated arbitrary file write in ar
Same vendor: bugsink
-
CVE-2026-47716
Bugsink: Issue bulk actions can affect another project’s iss -
CVE-2026-47715
Bugsink: Issue event views can show an event from another pr -
CVE-2026-47728
Bugsink: Project scoping missing in sourcemap and debug-file -
CVE-2026-44502
Bugsink: SSRF bypass in `validate_webhook_url` -
CVE-2026-40162
Bugsink affected by authenticated arbitrary file write in ar
Same weakness: CWE-400
-
CVE-2026-76821
OpenCTI: User-Controlled ReDoS in JSON Ingestion Mapper -
CVE-2026-88975
Http4s: Ember HTTP/2 buffers a frame's declared payload befo -
CVE-2026-69202
Http4s Ember HTTP/2: unbounded inbound body buffering -
CVE-2026-69203
Http4s Ember HTTP/2: does not enforce SETTINGS_MAX_CONCURREN -
CVE-2026-69213
Http4s Ember HTTP/2: unbounded outbound frame queue
V. Comments for CVE-2026-53954
No comments yet