CVE-2026-47728: medium-severity vulnerability in bugsink
Bugsink: Project scoping missing in sourcemap and debug-file lookup
Published
E-mail alert when it lands in KEV, gets a public PoC or its score goes up.
13Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 4.3epss 0.2%
Bugsink is a self-hosted error tracking tool. Prior to 2.2.0, Bugsink resolved sourcemaps and debug files by debug ID without scoping that lookup to the project that owned the uploaded metadata. An authenticated user with access to one project could cause event processing in that project to use sourcemap/debug-file metadata uploaded for another project in the same Bugsink instance, if the same debug ID was referenced. This vulnerability is fixed in 2.2.0.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
Affected products
bugsink · bugsinkRelated CVEs — bugsink
In the same product, most dangerous first.
CVE-2025-54433HIGHBugsink is vulnerable to Path Traversal attacks via event_id in ingestionEPSS 0.7%CVE-2026-53954MEDIUMBugsink: DOS using large numbers of event tagsEPSS 0.6%CVE-2025-64508HIGHBugsink vulnerable to unauthenticated remote DoS via crafted Brotli inputEPSS 0.5%CVE-2025-64509HIGHBugsink vulnerable to unauthenticated remote DoS via crafted Brotli input (via CPU)EPSS 0.3%CVE-2026-27614CRITICALBugsink is vulnerable to Stored XSS via Pygments fallback in stacktrace renderingEPSS 0.3%CVE-2026-40162HIGHBugsink affected by authenticated arbitrary file write in artifactbundle/assembleEPSS 0.3%