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