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.
CVE-2026-53954
MEDIUMPre-NVD 4.34.3
EchelonGraph scoreLOW confidence
This medium-severity CVE scores 4.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.1%, top 82% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
Triggered by: NVD CVSS baseline
Sources: epss, secondary
4.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
- Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 4.3Exploit: None knownExposed: 0
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 4.3
- EG Score
- 4.3(low)
- EG Risk
- 19(Track)EG Risk 19/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity43% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 25%
- KEV
- Not listed
Published
June 5, 2026
Last Modified
September 15, 2026
Advisory Details (4)
Auto-updated Sep 15, 2026Patch available. Sources: github, github_commit, github_release.
github_release Patch Available
2.2.2
Patch available: bugsink/bugsink 2.2.2
https://github.com/bugsink/bugsink/releases/tag/2.2.2github_commit Patch Available
commit 8dca571b9e66 (bugsink/bugsink)
Patch available: bugsink/bugsink 2.2.2 (contains commit 8dca571b9e66)
https://github.com/bugsink/bugsink/commit/8dca571b9e66c535ed4885465db820824e7c491agithub_commit Patch Available
commit 1d0539fefcd1 (bugsink/bugsink)
Patch available: bugsink/bugsink 2.2.2 (contains commit 1d0539fefcd1)
https://github.com/bugsink/bugsink/commit/1d0539fefcd1a796143d15d84053b1c0122ef8c7github Patch Available
DOS using large numbers of event tags · Advisory · bugsink/bugsink · GitHub
https://github.com/bugsink/bugsink/security/advisories/GHSA-5x67-j5xg-c5gjVendor Advisories for CVE-2026-53954(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(1 across 1 ecosystem)
PyPI(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| bugsink | 0.0.1 ... 2.2.1 (61 versions) | 2.2.2 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 7× in last 7d / 7× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-09-20 20:16 UTCEPSS rescore
- 2026-09-18 19:28 UTCEPSS rescore
- 2026-09-17 19:31 UTCEPSS rescore
- 2026-09-16 14:08 UTCEPSS rescore
- 2026-09-15 20:47 UTCEG score recompute
- 2026-09-15 19:50 UTCEG score recompute
- 2026-09-15 18:37 UTCEG score recompute
- 2026-07-31 05:12 UTCEG score recompute
- 2026-07-26 21:52 UTCEG score recompute
- 2026-07-23 03:19 UTCEG score recompute
- 2026-06-14 23:18 UTCEPSS rescore
- 2026-06-13 23:00 UTCEPSS rescore
- 2026-06-12 20:11 UTCEG score recompute
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-53954?
CVE-2026-53954 is a medium vulnerability published on June 5, 2026. 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…
When was CVE-2026-53954 disclosed?
CVE-2026-53954 was first published in the National Vulnerability Database on June 5, 2026, with the most recent update on September 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-53954 actively exploited?
CVE-2026-53954 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 74.5% of all scored CVEs.
What is the CVSS score of CVE-2026-53954?
CVE-2026-53954 has a CVSS v3 base score of 4.3 (NVD). The EG score is currently aggregating — additional source signals are being incorporated as they become available..
How do I remediate CVE-2026-53954?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53954, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-53954
Is Your Infrastructure Affected by CVE-2026-53954?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.