Approved changes feed: RSS · Atom
cpe:2.3:a:bugsink:bugsink:*:*:*:*:*:*:*:*part: a version: * update: *
| Vendor | Bugsink (7487ba94-ff6c-50ff-9105-72cb5a87bbee) |
|---|---|
| Product | Bugsink (7a731472-4e5d-5b4b-b32c-ffc41e132714) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
Notes
Imported from gcve-enriched-dumps CVE data
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
pkg:github/bugsink/bugsink |
purl2cpe | 2026-07-28 16:41:05.582120 |
pkg:pypi/bugsink |
purl2cpe | 2026-07-28 16:41:05.582121 |
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2026-47728 |
vulnerable | 2026-06-08 08:05:12.229984 |
Bugsink: Project scoping missing in sourcemap and debug-file lookup
MEDIUM (4.3)
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.
Published: 2026-05-26T16:16:10.858Z
Updated: 2026-05-26T17:31:41.956Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-47716 |
vulnerable | 2026-06-08 08:05:12.229696 |
Bugsink: Issue bulk actions can affect another project’s issue if its UUID is known
LOW (3.1)
Bugsink is a self-hosted error tracking tool. Prior to 2.2.0, In affected versions, the issue list view authorizes access through the project in the URL, but applies the requested bulk action to the submitted issue IDs without also requiring those issues to belong to that project. This vulnerability is fixed in 2.2.0.
Published: 2026-05-26T16:23:34.591Z
Updated: 2026-05-27T13:45:33.896Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-47715 |
vulnerable | 2026-06-08 08:05:12.229436 |
Bugsink: Issue event views can show an event from another project if its UUID is known
LOW (3.1)
Bugsink is a self-hosted error tracking tool. Prior to 2.2.0, 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. The affected views include the stacktrace, details, and breadcrumbs pages for an issue event. This vulnerability is fixed in 2.2.0.
Published: 2026-05-26T16:22:23.720Z
Updated: 2026-05-28T13:59:29.137Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-44502 |
vulnerable | 2026-06-08 08:05:11.121345 |
Bugsink: SSRF bypass in `validate_webhook_url`
MEDIUM (4.3)
Bugsink is a self-hosted error tracking tool. Prior to 2.1.3, Bugsink’s webhook URL validation could be (partially) bypassed because of a mismatch in URL parsing. The original validation logic parsed webhook URLs with Python’s urllib.parse.urlparse, then sent the request with requests.post. For malformed inputs involving backslashes and @, those components can disagree about where the authority ends and which hostname is the real target. A URL may therefore appear to target an allowlisted public hostname during validation, while the HTTP client actually connects to a different host. This vulnerability is fixed in 2.1.3.
Published: 2026-05-26T16:13:32.350Z
Updated: 2026-05-27T17:21:38.121Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-40162 |
vulnerable | 2026-06-08 08:01:19.952499 |
Bugsink affected by authenticated arbitrary file write in artifactbundle/assemble
HIGH (7.1)
Bugsink is a self-hosted error tracking tool. In 2.1.0, an authenticated file write vulnerability was identified in Bugsink 2.1.0 in the artifact bundle assembly flow. A user with a valid authentication token could cause the application to write attacker-controlled content to a filesystem location writable by the Bugsink process. This vulnerability is fixed in 2.1.1.
Published: 2026-04-10T17:02:58.985Z
Updated: 2026-04-10T18:30:44.339Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-27614 |
vulnerable | 2026-06-08 07:53:22.663148 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2025-64509 |
vulnerable | 2026-06-08 07:39:19.871112 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2025-64508 |
vulnerable | 2026-06-08 07:39:19.870826 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2025-54433 |
vulnerable | 2026-06-08 07:33:12.593969 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.
Inspect record JSON
Open this panel to browse, search, copy or download the JSON record.