Bugsink issue event pages accept a direct event identifier from the URL and, in affected versions, look up that event without also requiring it to belong to the issue in the URL.
This is a project-boundary authorization issue: a logged-in user with access to one project can view another project’s event data through an issue they are allowed to access. However, the issue is mitigated by two factors. First, the attacker needs to already know a valid target event UUID; there is no event enumeration path here, and guessing UUIDs is not practical. Second, Bugsink is commonly self-hosted within a single trust domain, and Hosted Bugsink gives each tenant a separate Bugsink instance, so cross-project access does not normally imply cross-tenant access.
The affected views include the stacktrace, details, and breadcrumbs pages for an issue event.
This has been fixed by requiring direct event lookups to match both the authorized issue and the project.
Low-severity cross-project event data exposure, requiring authentication and prior knowledge of a valid event UUID.
| Score | Percentile |
|---|---|
| 0.03% | 8.52% |
| Base score | Version | Severity | Vector |
|---|---|---|---|
| 3.1 | 3.1 | — |
|
| Type | Value |
|---|---|
| GHSA | GHSA-vx2f-6m6h-9frf ↗ |
| CVE | CVE-2026-47715 ↗ |
| CWE id | Name |
|---|---|
| CWE-639 | Authorization Bypass Through User-Controlled Key |
Vulnerable version ranges and first patched releases as published by GitHub.
| Ecosystem | Package | Vulnerable range | First patched | Vulnerable functions |
|---|---|---|---|---|
| pip | bugsink | < 2.2.0 | 2.2.0 | — |