Is CVE-2026-47728 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-47728 being exploited in the wild.

How severe is CVE-2026-47728?

Medium severity, with a CVSS score of 4.3, published 26 May 2026.

Which products and versions are affected?

Bugsink < 2.2.0, <= 2.1.3; bugsink (PyPI) ECOSYSTEM:introduced=0,fixed=2.2.0.

Is there a fix for CVE-2026-47728?

Yes. bugsink (PyPI): upgrade to 2.2.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-47728 attacked?

It is attacked over the network, in a network appliance.

Am I affected by CVE-2026-47728?

Check whether you run Bugsink or bugsink (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-47728: Bugsink missing project scoping in sourcemap and debug file lookup

Q: Which products and versions are affected?

Bugsink < 2.2.0, <= 2.1.3; bugsink (PyPI) ECOSYSTEM:introduced=0,fixed=2.2.0.

Q: Is there a fix for CVE-2026-47728?

Yes. bugsink (PyPI): upgrade to 2.2.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2026-47728 attacked?

It is attacked over the network, in a network appliance.

Q: Am I affected by CVE-2026-47728?

Check whether you run Bugsink or bugsink (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-47728 · Severity: medium · CVSS 4.3 · Published 2026-05-26

Bugsink, an error-tracking and log-aggregation tool, failed to properly isolate data between different projects on the same server. An authorized user of one project could potentially view sensitive source code or debugging information belonging to a different project if they knew the specific identification numbers for those files. This issue primarily affects self-hosted installations where multiple internal teams share a single server.

Technologies: Bugsink, bugsink (PyPI). Vendors: Bugsink, PyPI.

Quick answers

Is CVE-2026-47728 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-47728 being exploited in the wild.
How severe is CVE-2026-47728?: Medium severity, with a CVSS score of 4.3, published 26 May 2026.
Which products and versions are affected?: Bugsink < 2.2.0, <= 2.1.3; bugsink (PyPI) ECOSYSTEM:introduced=0,fixed=2.2.0.
Is there a fix for CVE-2026-47728?: Yes. bugsink (PyPI): upgrade to 2.2.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-47728 attacked?: It is attacked over the network, in a network appliance.
Am I affected by CVE-2026-47728?: Check whether you run Bugsink or bugsink (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

bugsink (PyPI): upgrade to 2.2.0 or later
```
pip install "bugsink>=2.2.0"
```

Technical details

A missing authorization check (CWE-862) in Bugsink versions prior to 2.2.0 allowed authenticated users to access sourcemaps and debug-file metadata across project boundaries. The application resolved these files using only a 'debug ID' without verifying that the requesting project owned the metadata. An attacker with access to one project could trigger event processing that references a debug ID from another project, leading to the disclosure of source context or symbolication data. This vulnerability is mitigated in Hosted Bugsink due to tenant isolation but affects self-hosted multi-project instances. The fix in version 2.2.0 introduces proper project scoping for these lookups.

Affected products

Bugsink Bugsink < 2.2.0

Identifiers

CVE-2026-47728
GHSA-5389-f7vh-wxj8
PYSEC-2026-2402

Timeline

2026-05-21: disclosed: Initial disclosure by maintainer
2026-05-26: advisory: NVD publication date
2026-06-05: advisory: GitHub Advisory reviewed and updated

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.