CVE-2026-47728: Bugsink Remote Code Execution Vulnerability

MODERATE
Advisory Identifier: GHSA-5389-f7vh-wxj8
Share
CVSS 4.3
CWE-862
Published
Advisory Summary

CVE-2026-47728 is a MODERATE (CVSS 4.3) remote code execution vulnerability (CWE-862: Missing Authorization) affecting Bugsink libraries in the PyPI ecosystem. The issue involves project scoping missing in sourcemap and debug-file lookup. Remediation is available by upgrading affected packages to version 2.2.0.

CVE-2026-47728 at a Glance

CVE Identifier CVE-2026-47728
GHSA Identifier GHSA-5389-f7vh-wxj8
Severity MODERATE
CVSS v3.1 Base Score 4.3
CWE Classification CWE-862: Missing Authorization
Affected Product Bugsink
Package Ecosystem PyPI
Published Date
Last Updated

Security Impact

CVSS: 4.3

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required Low (PR:L)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality Low (C:L)
Integrity None (I:N)
Availability None (A:N)

How to Fix CVE-2026-47728

To remediate this vulnerability, upgrade all affected Bugsink dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

bugsink fixed: 2.2.0 
pip install bugsink>=2.2.0
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release: 

pip show bugsink

How to Check if You Are Affected

To determine whether your Python environment is affected by CVE-2026-47728, inspect your installed packages using pip:

pip show bugsink

Analyze the terminal output to locate any version of Bugsink in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 2.2.0), your application is affected.

Note: The pip show bugsink command checks currently installed packages in your active Python environment.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-862: Missing Authorization, where the product does not perform an authorization check when an actor attempts to access a resource or perform an action. In Bugsink, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### Summary Bugsink before 2.2.0 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. ### Impact This could disclose source context or symbolication-derived context from another project on the same Bugsink instance. For sourcemaps, the documented upload flow used `sentry-cli sourcemaps upload` with `--project=ignoredfornow`. In other words, Bugsink did not historically treat the project value supplied during sourcemap upload as meaningful project ownership. This was documented, but at the same time the `sentry-cli`, which requires project as a parameter, was the recommended mechanism for uploads. This could reasonably lead people to expect that sourcemaps uploads would respect the provided project-boundary. For minidumps/debug files specifically, the affected functionality also required `FEATURE_MINIDUMPS` to be enabled. That feature was marked experimental. The practical impact is further limited by Bugsink’s deployment model: self-hosted instances are commonly operated within a single organization/trust domain, and Hosted Bugsink uses separate Bugsink instances per tenant. The issue does not cross Hosted Bugsink tenant boundaries. ### Affected Versions 2.1.3 and earlier are affected. ### Patched Versions 2.2.0 fixes this issue. ### Post-Upgrade Notes After upgrading, upload sourcemaps/debug files with project information. To remove legacy projectless sourcemap metadata immediately, run, after upgrading: ``` bugsink-manage delete_legacy_sourcemaps ```

CVE-2026-47728 Affected Bugsink Versions

1 component(s)
Fixed Versions:
2.2.0
Product / Package Ecosystem Affected Versions Fixed Version
bugsink
pypi/bugsink
PyPI
< 2.2.0
2.2.0

References

GitHub Advisory / Wiki ADVISORY
https://github.com/bugsink/bugsink/security/advisories/GHSA-5389-f7vh-wxj8
NVD — CVE-2026-47728 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-47728
Bugsink Source Repository REPOSITORY
https://github.com/bugsink/bugsink
Bugsink Release RELEASE
https://github.com/bugsink/bugsink/releases/tag/2.2.0

Frequently Asked Questions

What is CVE-2026-47728?
CVE-2026-47728 is a security vulnerability in Bugsink involving Project scoping missing in sourcemap and debug-file lookup under CWE-862: Missing Authorization.
Which Bugsink versions are affected?
Affected versions include releases prior to 2.2.0 across affected packages: bugsink.
What version fixes CVE-2026-47728?
Upgrading to 2.2.0 (or the latest patched release for your respective branch) resolves the vulnerability.
Is bugsink affected?
Yes, bugsink is affected in releases prior to 2.2.0. Upgrade your dependency to 2.2.0 or later.
What is the CVSS score of CVE-2026-47728?
CVE-2026-47728 has a CVSS v3.1 base score of 4.3 (MODERATE) with vector string CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N.
What CWE is associated with CVE-2026-47728?
CVE-2026-47728 is classified under CWE-862: Missing Authorization (The product does not perform an authorization check when an actor attempts to access a resource or perform an action.).
How can I check PyPI dependencies for CVE-2026-47728?
Run the dependency tree command: 'pip show bugsink'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-5389-f7vh-wxj8",
  "modified" : "2026-06-05T21:44:33Z",
  "published" : "2026-06-05T21:44:33Z",
  "aliases" : [ "CVE-2026-47728" ],
  "summary" : "Bugsink: Project scoping missing in sourcemap and debug-file lookup",
  "details" : "### Summary\n\nBugsink before 2.2.0 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.\n\n### Impact\n\nThis could disclose source context or symbolication-derived context from another project on the same Bugsink instance.\n\nFor sourcemaps, the documented upload flow used `sentry-cli sourcemaps upload` with `--project=ignoredfornow`. In other words, Bugsink did not historically treat the project value supplied during sourcemap upload as meaningful project ownership. This was documented, but at the same time the `sentry-cli`, which requires project as a parameter, was the recommended mechanism for uploads. This could reasonably lead people to expect that sourcemaps uploads would respect the provided project-boundary.\n\nFor minidumps/debug files specifically, the affected functionality also required `FEATURE_MINIDUMPS` to be enabled. That feature was marked experimental.\n\nThe practical impact is further limited by Bugsink’s deployment model: self-hosted instances are commonly operated within a single organization/trust domain, and Hosted Bugsink uses separate Bugsink instances per tenant. The issue does not cross Hosted Bugsink tenant boundaries.\n\n### Affected Versions\n2.1.3 and earlier are affected.\n\n### Patched Versions\n2.2.0 fixes this issue.\n\n### Post-Upgrade Notes\n\nAfter upgrading, upload sourcemaps/debug files with project information.\n\nTo remove legacy projectless sourcemap metadata immediately, run, after upgrading:\n\n```\nbugsink-manage delete_legacy_sourcemaps\n```",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "PyPI",
      "name" : "bugsink"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "2.2.0"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/bugsink/bugsink/security/advisories/GHSA-5389-f7vh-wxj8"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-47728"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/bugsink/bugsink"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/bugsink/bugsink/releases/tag/2.2.0"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-862" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-06-05T21:44:33Z",
    "nvd_published_at" : "2026-05-26T17:16:53Z"
  }
}