Cross-project issue modification via unscoped bulk actions
Published May 26, 2026 · Updated May 26, 2026
Authorization bypass in Bugsink before 2.2.0 allows remote authenticated users to modify issue states across project boundaries. The issue-list bulk-action view authorizes the project named in the URL, then applies actions to submitted issue UUIDs without verifying project ownership. Exploitation requires membership in one project and prior knowledge of a valid UUID from another; it changes only that issue's state and does not cross hosted tenant instances.
Summary
What happened
Authorization bypass in Bugsink before 2.2.0 allows remote authenticated users to modify issue states across project boundaries. The issue-list bulk-action view authorizes the project named in the URL, then applies actions to submitted issue UUIDs without verifying project ownership. Exploitation requires membership in one project and prior knowledge of a valid UUID from another; it changes only that issue's state and does not cross hosted tenant instances.
The record
- CVE
- CVE-2026-47716
- Published
- May 26, 2026
- Updated
- May 26, 2026
- Vendor
- Bugsink
- Product
- Bugsink
- Classifications
- CWE-639, T1565.001
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- May 26, 2026CVE publishedPublication date reported by the CVE source.
- May 26, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 2.2.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo