# CVE-2026-115321: Bytebase UpdateIssueComment authorization bypass

Source: https://junglewise.ai/threats/cve-2026-115321-bytebase-before-3-16-0-contains-an-authorization-bypass  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-10-22. Updated: 2026-10-22  
License: CC BY 4.0 with a link back

CVE-2026-115321 · Severity: medium · CVSS 4.3 · Published 2026-10-22

Bytebase is a database governance platform that controls schema changes and access across databases. A low-privileged user with any project role (including read-only) can modify issue comments in other projects they should not access, potentially altering collaboration records and decisions. An attacker can exploit this by referencing a comment from another project and modifying its content.

Technologies: [Bytebase](https://junglewise.ai/threats/technologies/bytebase). Vendors: [Bytebase](https://junglewise.ai/threats/vendors/bytebase).

## Quick answers

**Is CVE-2026-115321 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-115321 being exploited in the wild.

**How severe is CVE-2026-115321?** Medium severity, with a CVSS score of 4.3, published 22 October 2026.

**Which products and versions are affected?** Bytebase before 3.16.0.

**Is there a fix for CVE-2026-115321?** Yes: fixed in 3.16.0. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-115321 attacked?** It is attacked over the network, in a web application.

**Am I affected by CVE-2026-115321?** Check whether you run Bytebase at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## How to fix

- Fixed in 3.16.0

## Technical details

An authorization bypass in the UpdateIssueComment handler fails to validate that the user's project matches the target comment's project. An attacker with any project role can supply a foreign comment UID and set their own project's issue as parent to overwrite comments in other projects they lack access to. The vulnerability requires an authenticated user but allows cross-project privilege escalation.

## Affected products

- Bytebase Bytebase before 3.16.0

## Timeline

- 2026-10-22: disclosed

## References

- [https://github.com/bytebase/bytebase](https://github.com/bytebase/bytebase)
- [https://github.com/bytebase/bytebase/blob/3.15.1/backend/api/v1/issue_service.go](https://github.com/bytebase/bytebase/blob/3.15.1/backend/api/v1/issue_service.go)

## Related threats

- [Bytebase authentication bypass in GitLab login](https://junglewise.ai/threats/cve-2022-51026-bytebase-0-12-0-before-1-0-1-contains-an-authentication-bypass)
- [Bytebase authorization bypass in GetTaskRunLog and GetTaskRunSession](https://junglewise.ai/threats/cve-2026-115322-bytebase-before-3-16-0-contains-an-authorization-bypass)