CVE-2026-47728
Bugsink: Project scoping missing in sourcemap and debug-file lookup
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.
Attack profile
How easy it is to exploit
- Attack vector
- Network
- Complexity
- Low
- Privileges needed
- Low
- User interaction
- None
What an attacker can affect
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
Exploit likelihood
What each source reports
CVE List Score used
Bugsink: Project scoping missing in sourcemap and debug-file lookup
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.
- Record
CVE-2026-47728- CVSS 3.1
- 4.3 Medium
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N - Weakness
- CWE-862
- Updated
- 2026-11-02
EUVDEUVD-2026-31860
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.
- Record
EUVD-2026-31860- CVSS 3.1
- 4.3 Medium
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N - Updated
- 2026-11-02
GitHub AdvisoriesGHSA-5389-f7vh-wxj8
Bugsink: Project scoping missing in sourcemap and debug-file lookup
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
- Record
GHSA-5389-f7vh-wxj8- CVSS 3.1
- 4.3 Medium
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N - Weakness
- CWE-862
- Updated
- 2026-11-02
NVD
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.
- Record
CVE-2026-47728- CVSS 3.1
- 4.3 Medium
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N - Weakness
- CWE-862
- Updated
- 2026-11-02
OSV
Bugsink: Project scoping missing in sourcemap and debug-file lookup
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.
- Record
CVE-2026-47728- CVSS 3.1
- 4.3 Medium
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N - Weakness
- CWE-862
- Updated
- 2026-11-02
OSVGHSA-5389-f7vh-wxj8
Bugsink: Project scoping missing in sourcemap and debug-file lookup
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
- Record
GHSA-5389-f7vh-wxj8- CVSS 3.1
- 4.3 Medium
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N - Weakness
- CWE-862
- Updated
- 2026-11-02
OSVPYSEC-2026-2402
Bugsink: Project scoping missing in sourcemap and debug-file lookup
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
- Record
PYSEC-2026-2402- CVSS 3.1
- 4.3 Medium
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N - Updated
- 2026-11-02
Affected products
Affected packages
| Package | Affected | Fixed |
|---|---|---|
bugsinkPyPI |
before 2.2.0 | 2.2.0 |
bugsinkPyPI |
before 2.2.0, plus listed versions 0.0.10.1.120.1.130.1.140.1.15 Show 45 moreShow less0.1.160.1.170.1.180.1.190.1.201.0.01.0.11.1.01.1.11.1.21.2.01.3.01.4.01.4.11.4.21.4.31.5.01.5.11.5.21.5.31.5.41.5.51.6.01.6.11.6.21.6.31.6.41.7.01.7.11.7.21.7.31.7.41.7.51.7.62.0.02.0.0a12.0.12.0.102.0.112.0.122.0.132.0.142.0.22.0.32.0.4 |
2.2.0 |
History
| Recorded | Changed | Sources |
|---|---|---|
| aliases, published | EUVD | |
| first indexed | CVE List, GitHub Advisories, NVD, OSV |
Dates are when Every CVE recorded each change. Upstream dates may differ.
In short
CVE-2026-47728 is a medium vulnerability (CVSS 4.3) in Bugsink, published May 26, 2026. No source lists public exploit code. EPSS puts the chance of exploitation in the next 30 days at 0.18%, the 7th percentile. Fixed in bugsink 2.2.0.
References
github.com/bugsink/bugsink/security/advisories/GHSA-5389-f7vh-wxj8
nvd.nist.gov/vuln/detail/CVE-2026-47728
pypi.org/project/bugsink
Left out here: 9 versions. The JSON record has them.