CVE-2026-47715: Bugsink: Issue event views can show an event from another project if its UUID is known
Description 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.
Published Jun 5, 2026
Affected packages
bugsink
- Ecosystem
- PyPI
- Affected
- < 2.2.0
- Fixed in
- 2.2.0
- Check
pip show bugsink
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Description
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.
Impact
Low-severity cross-project event data exposure, requiring authentication and prior knowledge of a valid event UUID.
Credited to nuiifornet.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More PyPI vulnerabilities
All PyPI entriesCVE-2026-47716
Bugsink: Issue bulk actions can affect another project’s issue if its UUID is known
low3.1Jun 5, 2026CVE-2026-47728
Bugsink: Project scoping missing in sourcemap and debug-file lookup
medium4.3Jun 5, 2026CVE-2026-53954
Bugsink: DOS using large numbers of event tags
medium4.3Jun 5, 2026CVE-2026-44502
Bunsink has an SSRF bypass in `validate_webhook_url`
medium4.3May 8, 2026CVE-2026-40162
Bugsink affected by authenticated arbitrary file write in artifactbundle/assemble
high7.1Apr 10, 2026CVE-2026-27614
Bugsink is vulnerable to Stored XSS via Pygments fallback in stacktrace rendering
critical9.3Feb 25, 2026
