Every CVE Search/ Get API key

CVE-2026-47716

Bugsink: Issue bulk actions can affect another project’s issue if its UUID is known

3.1 LowFix available

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.

Attack profile

How easy it is to exploit

Attack vector
Network
Complexity
High
Privileges needed
Low
User interaction
None

What an attacker can affect

Confidentiality
None
Integrity
Low
Availability
None

Exploit likelihood

0.15%Up 0.1 points since May 27, 2026
90%50%10%1%

What each source reports

CVE List Score used 3.1

Bugsink: Issue bulk actions can affect another project’s issue if its UUID is known

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.

Record
CVE-2026-47716
CVSS 3.1
3.1 LowCVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:N
Weakness
CWE-639
Updated
2026-11-02
EUVDEUVD-2026-31862 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.

Record
EUVD-2026-31862
CVSS 3.1
3.1 LowCVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:N
Updated
2026-11-02
GitHub AdvisoriesGHSA-g5vc-q7qc-v939 3.1

Bugsink: Issue bulk actions can affect another project’s issue if its UUID is known

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.

Record
GHSA-g5vc-q7qc-v939
CVSS 3.1
3.1 LowCVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:N
Weakness
CWE-639
Updated
2026-11-02
NVD 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.

Record
CVE-2026-47716
CVSS 3.1
3.1 LowCVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:N
Weakness
CWE-639
Updated
2026-11-02
OSV 3.1

Bugsink: Issue bulk actions can affect another project’s issue if its UUID is known

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.

Record
CVE-2026-47716
CVSS 3.1
3.1 LowCVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:N
Weakness
CWE-639
Updated
2026-11-02
OSVGHSA-g5vc-q7qc-v939 3.1

Bugsink: Issue bulk actions can affect another project’s issue if its UUID is known

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.

Record
GHSA-g5vc-q7qc-v939
CVSS 3.1
3.1 LowCVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:N
Weakness
CWE-639
Updated
2026-11-02
OSVPYSEC-2026-2406 3.1

Bugsink: Issue bulk actions can affect another project’s issue if its UUID is known

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.

Record
PYSEC-2026-2406
CVSS 3.1
3.1 LowCVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:N
Updated
2026-11-02

Affected products

Affected packages

Affected packages
PackageAffectedFixed
bugsink
PyPI
 before 2.2.0
2.2.0
bugsink
PyPI
 before 2.2.0, plus listed versions
0.0.10.1.120.1.130.1.140.1.15
Show 45 moreShow less
0.1.160.1.170.1.180.1.190.1.201.0.01.0.11.1.01.1.11.1.21.2.01.3.01.4.01.4.11.4.21.4.31.5.01.5.11.5.21.5.31.5.41.5.51.6.01.6.11.6.21.6.31.6.41.7.01.7.11.7.21.7.31.7.41.7.51.7.62.0.02.0.0a12.0.12.0.102.0.112.0.122.0.132.0.142.0.22.0.32.0.4
2.2.0

History

History
RecordedChangedSources
aliases, publishedEUVD
first indexedCVE List, GitHub Advisories, NVD, OSV

Dates are when Every CVE recorded each change. Upstream dates may differ.

In short

CVE-2026-47716 is a low vulnerability (CVSS 3.1) in Bugsink, published May 26, 2026. No source lists public exploit code. EPSS puts the chance of exploitation in the next 30 days at 0.15%, the 3rd percentile. Fixed in bugsink 2.2.0.

References

This page doesn't list everything

Left out here: 9 versions. The JSON record has them.

Pages All vulnerabilities Browse Docs Sources Guide Get API key
MoveEnter Open