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

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

3.1 · CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:N

EPSS

• CVE-2026-47716: 0.15% estimated exploitation activity in the next 30 days; percentile 3.91 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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…

Published by the source

5 Jun 2026, 21:43 UTC

Last modified by the source

13 Jul 2026, 16:42 UTC

Source last checked

26 Oct 2026, 13:42 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-g5vc-q7qc-v939

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-g5vc-q7qc-v939

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-47716

Advisory: Bugsink: Issue bulk actions can affect another project’s issue if its UUID is known
IDs: CVE-2026-47716, GHSA-g5vc-q7qc-v939
Record: https://patchnext.com/advisories/cve-2026-47716 (revision 2, source checked 26 Oct 2026, 13:42 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Low (CVSS 3.1)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: bugsink 2.2.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI bugsink: affected < 2.2.0; fixed in 2.2.0

## Suggested inspection (read-only)
- `python -m pip show bugsink`: prints the installed version. Run with the environment that serves production active.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on bugsink.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-g5vc-q7qc-v939 (OSV record GHSA-g5vc-q7qc-v939 lists affected ranges: PyPI bugsink >=0 <2.2.0 (fixed))
- Verified: https://github.com/advisories/GHSA-g5vc-q7qc-v939 (GitHub-reviewed advisory GHSA-g5vc-q7qc-v939 lists affected ranges: PyPI bugsink >=0 <2.2.0)

Commands are suggestions: review each one before running it.