CVE-2026-47715
Project-Boundary Authorization Issue in Bugsink Prior to 2.2.0
Publication date: 2026-05-26
Last updated on: 2026-05-26
Assigner: GitHub, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| bugsink | bugsink | to 2.1.3 (exc) |
| bugsink | bugsink | 2.2.0 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-639 | The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data. |
Attack-Flow Graph
AI Powered Q&A
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
This vulnerability allows a logged-in user with access to one project to view event data from another project if they know the event's UUID, resulting in unauthorized access to potentially sensitive information across project boundaries.
Such unauthorized access to data could potentially impact compliance with data protection regulations like GDPR or HIPAA, which require strict controls on access to personal or sensitive data to prevent unauthorized disclosure.
However, the vulnerability requires authentication and prior knowledge of event UUIDs, and Bugsink is often self-hosted within a single trust domain or uses separate instances per tenant, which may reduce the risk of cross-tenant data exposure.
Overall, while the vulnerability represents an authorization bypass that could lead to unauthorized data access, its practical impact on compliance depends on the deployment context and the sensitivity of the data involved.
Can you explain this vulnerability to me?
This vulnerability affects Bugsink, a self-hosted error tracking tool, in versions prior to 2.2.0. The issue is an authorization bypass where issue event pages accept a direct event identifier from the URL and look up that event without verifying it belongs to the issue or project in the URL. As a result, a logged-in user with access to one project can view event data from another project if they know the event's UUID. This affects views such as stacktrace, details, and breadcrumbs pages for issue events.
How can this vulnerability impact me? :
The vulnerability allows a user with access to one project to view event data from another project without proper authorization, potentially exposing sensitive debugging information across project boundaries. However, exploitation requires prior knowledge of a valid event UUID, making random guessing impractical. The impact is considered low severity because it requires authentication, has high attack complexity, and does not allow modification of data.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability involves unauthorized access to event data across projects in Bugsink versions prior to 2.2.0 by using known event UUIDs. Detection would involve verifying if event views are accessible across project boundaries without proper authorization.
Since the issue requires knowledge of valid event UUIDs and authentication, detection can include reviewing access logs for cross-project event access patterns or attempts to access event URLs with event UUIDs that do not belong to the authorized project.
No specific commands are provided in the available resources to detect this vulnerability on your network or system.
What immediate steps should I take to mitigate this vulnerability?
The primary mitigation step is to upgrade Bugsink to version 2.2.0 or later, where this vulnerability has been fixed by enforcing that event lookups must belong to the authorized issue and project.
Additionally, users are advised to upgrade sourcemap uploads to include project slugs and remove legacy unscoped sourcemaps by running the appropriate cleanup commands as described in the release notes.