CVE-2026-47728 — bugsink
MEDIUMCVE-2026-47728 is a medium-severity (CVSS 4.3) CWE-862 vulnerability in bugsink. A fix is available for bugsink — see the affected versions and patch details below.
Bugsink: Project scoping missing in sourcemap and debug-file lookup
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2026-47728.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
CVE-2026-47728 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.
Where this sits among everything scored
Of 390,807 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.
Real-World Exposure
bugsinkReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.
Description
Summary
Bugsink before 2.2.0 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.
Impact
This could disclose source context or symbolication-derived context from another project on the same Bugsink instance.
For sourcemaps, the documented upload flow used sentry-cli sourcemaps upload with --project=ignoredfornow. In other words, Bugsink did not historically treat the project value supplied during sourcemap upload as meaningful project ownership. This was documented, but at the same time the sentry-cli, which requires project as a parameter, was the recommended mechanism for uploads. This could reasonably lead people to expect that sourcemaps uploads would respect the provided project-boundary.
For minidumps/debug files specifically, the affected functionality also required FEATURE_MINIDUMPS to be enabled. That feature was marked experimental.
The practical impact is further limited by Bugsink’s deployment model: self-hosted instances are commonly operated within a single organization/trust domain, and Hosted Bugsink uses separate Bugsink instances per tenant. The issue does not cross Hosted Bugsink tenant boundaries.
Affected Versions
2.1.3 and earlier are affected.
Patched Versions
2.2.0 fixes this issue.
Post-Upgrade Notes
After upgrading, upload sourcemaps/debug files with project information.
To remove legacy projectless sourcemap metadata immediately, run, after upgrading:
bugsink-manage delete_legacy_sourcemaps
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐍PyPI | bugsink | all versions | 2.2.0pip install --upgrade 'bugsink==2.2.0' |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for bugsink, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update bugsink to 2.2.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-47728 is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.
Frequently Asked Questions
Is CVE-2026-47728 in your dependencies?
Find it across PyPI, including transitive dependencies.