CVE-2026-47716: Bugsink Issue Bulk Actions Can Affect Vulnerability

LOW
Advisory Identifier: GHSA-g5vc-q7qc-v939
Share
CVSS 3.1
CWE-639
Published
Advisory Summary

CVE-2026-47716 is a LOW (CVSS 3.1) issue bulk actions can affect vulnerability (CWE-639: Authorization Bypass Through User-Controlled Key) affecting Bugsink libraries in the PyPI ecosystem. The issue involves issue bulk actions can affect another project’s issue if its uuid is known. Remediation is available by upgrading affected packages to version 2.2.0.

CVE-2026-47716 at a Glance

CVE Identifier CVE-2026-47716
GHSA Identifier GHSA-g5vc-q7qc-v939
Severity LOW
CVSS v3.1 Base Score 3.1
CWE Classification CWE-639: Authorization Bypass Through User-Controlled Key
Affected Product Bugsink
Package Ecosystem PyPI
Published Date
Last Updated

Security Impact

CVSS: 3.1

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

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

How to Fix CVE-2026-47716

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-47716, 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-639: Authorization Bypass Through User-Controlled Key, where 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. 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

### Description Bugsink’s issue list supports bulk actions such as resolving or muting selected issues. 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 is a project-boundary authorization issue: a logged-in user with access to one project can change the state of an issue in another project. However, the issue is mitigated by two factors. First, the attacker needs to already know a valid target issue UUID; there is no issue 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. This has been fixed by requiring bulk issue actions to operate only on issues belonging to the authorized project. ### Impact Low-severity cross-project issue state modification, requiring authentication and prior knowledge of a valid issue UUID.

CVE-2026-47716 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-g5vc-q7qc-v939
NVD — CVE-2026-47716 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-47716
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-47716?
CVE-2026-47716 is a security vulnerability in Bugsink involving Issue bulk actions can affect another project’s issue if its UUID is known under CWE-639: Authorization Bypass Through User-Controlled Key.
Which Bugsink versions are affected?
Affected versions include releases prior to 2.2.0 across affected packages: bugsink.
What version fixes CVE-2026-47716?
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-47716?
CVE-2026-47716 has a CVSS v3.1 base score of 3.1 (LOW) with vector string CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:N.
What CWE is associated with CVE-2026-47716?
CVE-2026-47716 is classified under CWE-639: Authorization Bypass Through User-Controlled Key (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.).
How can I check PyPI dependencies for CVE-2026-47716?
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-g5vc-q7qc-v939",
  "modified" : "2026-06-05T21:43:56Z",
  "published" : "2026-06-05T21:43:56Z",
  "aliases" : [ "CVE-2026-47716" ],
  "summary" : "Bugsink: Issue bulk actions can affect another project’s issue if its UUID is known",
  "details" : "### Description\nBugsink’s issue list supports bulk actions such as resolving or muting selected issues. 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.\n\nThis is a project-boundary authorization issue: a logged-in user with access to one project can change the state of an issue in another project. However, the issue is mitigated by two factors. First, the attacker needs to already know a valid target issue UUID; there is no issue 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.\n\nThis has been fixed by requiring bulk issue actions to operate only on issues belonging to the authorized project.\n\n### Impact\n\nLow-severity cross-project issue state modification, requiring authentication and prior knowledge of a valid issue UUID.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:L/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-g5vc-q7qc-v939"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-47716"
  }, {
    "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-639" ],
    "severity" : "LOW",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-06-05T21:43:56Z",
    "nvd_published_at" : "2026-05-26T17:16:52Z"
  }
}