# CVE-2026-47716: Bugsink: Issue bulk actions can affect another project’s issue if its UUID is known

> Attackers can perform bulk actions on issues in other projects if they know the issue UUID, bypassing project-level authorization checks.

- **Severity:** Low 3.1 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 26 May 2026
- **Updated:** 27 May 2026
- **Also known as:** GHSA-g5vc-q7qc-v939, PYSEC-2026-2406

## What is CVE-2026-47716?

CVE-2026-47716 is a low-severity missing authorization vulnerability in bugsink, published on 26 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

## Which versions are affected by CVE-2026-47716?

3 open source packages ship an affected version, including bugsink.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `bugsink` | PyPI | All versions | 2.2.0 |
| `bugsink` | PyPI | All versions | 2.2.0 |
| `bugsink` | PyPI | All versions | 2.2.0 |

## How do I fix CVE-2026-47716?

Upgrade bugsink to 2.2.0 or later.

## Is CVE-2026-47716 being exploited?

There is no known exploitation of CVE-2026-47716 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-47716 and fix it if it is affected.

What it is: CVE-2026-47716 is a low-severity missing authorization vulnerability in bugsink, published on 26 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-47716 in the wild and no public exploit code.

Affected packages and fixed versions:
- bugsink (PyPI): affected all versions; fixed in 2.2.0
- bugsink (PyPI): affected all versions; fixed in 2.2.0
- bugsink (PyPI): affected all versions; fixed in 2.2.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-47716/ (Markdown: https://insights.sbomify.com/CVE-2026-47716/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-47716
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-47716
- OSV: https://osv.dev/vulnerability/CVE-2026-47716

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-47716/
Summaries are generated and may contain mistakes; the official description above is the record.