Ingestion interruption via unbounded event-tag writes
Published Sep 15, 2026 · Updated Sep 15, 2026
Uncontrolled resource consumption in Bugsink 2.2.1 and earlier allows remote authenticated users to interrupt event ingestion via oversized tag sets. The ingestion path writes every attacker-supplied custom tag in one database transaction, monopolizing Bugsink's single writer and delaying other events. Exploitation requires a valid project DSN; the result is a temporary ingestion stall without data exposure, existing-event modification, or code execution.
Summary
What happened
Uncontrolled resource consumption in Bugsink 2.2.1 and earlier allows remote authenticated users to interrupt event ingestion via oversized tag sets. The ingestion path writes every attacker-supplied custom tag in one database transaction, monopolizing Bugsink's single writer and delaying other events. Exploitation requires a valid project DSN; the result is a temporary ingestion stall without data exposure, existing-event modification, or code execution.
The record
- CVE
- CVE-2026-53954
- Published
- Sep 15, 2026
- Updated
- Sep 15, 2026
- Vendor
- Bugsink
- Product
- Bugsink
- Classifications
- CWE-400, T1499.003
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 15, 2026CVE publishedPublication date reported by the CVE source.
- Sep 15, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 2.2.2
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo