CVE-2026-115322: Bytebase authorization bypass in GetTaskRunLog and GetTaskRunSession

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

Bytebase is a database governance platform that manages schema changes and access controls across databases. Versions before 3.16.0 contain an authorization flaw that allows authenticated users with access to one project to read execution logs, database session details, and rollback SQL from unrelated projects by providing foreign task or task run identifiers. This could expose sensitive database operation details and SQL code across project boundaries.</brief> <parameter name="technical_details">An authorization bypass exists in the GetTaskRunLog, GetTaskRunSession, and PreviewTaskRunRollback API endpoints that fails to properly validate project ownership before returning task run data. An authenticated attacker with permissions on one project can supply task or task run UIDs from other projects to access their execution logs, session information, and rollback SQL. The vulnerability requires authentication but impacts confidentiality across project boundaries.

Technologies: Bytebase. Vendors: Bytebase.

Quick answers

Is CVE-2026-115322 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-115322 being exploited in the wild.
How severe is CVE-2026-115322?
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-115322?
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-115322 attacked?
It is attacked over the network, in a web application.
Am I affected by CVE-2026-115322?
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

Affected products

  • Bytebase Bytebase before 3.16.0

Timeline

  • 2026-10-22: disclosed

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.