CVE-2026-115322 Bytebase before 3.16.0 Authorization Bypass via Rollout Service Task Run Handlers
Medium 5.3
Published
Updated
Check this codebase for CVE-2026-115322 and fix it if it is affected.
What it is: CVE-2026-115322 is a medium-severity vulnerability in bytebase, published on 22 Oct 2026.
Exploitation: There is no known exploitation of CVE-2026-115322 in the wild and no public exploit code.
Affected product: bytebase. No package-level version data is available, so check the vendor advisory linked from the reference page.
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-115322/ (Markdown: https://insights.sbomify.com/CVE-2026-115322/index.md)
- Exploited in the wild
- Not known
- Fix
- None listed
What is CVE-2026-115322?
CVE-2026-115322 is a medium-severity vulnerability in bytebase, published on 22 Oct 2026.
Official description
Bytebase before 3.16.0 contains an authorization bypass vulnerability in GetTaskRunLog, GetTaskRunSession and PreviewTaskRunRollback that allows authenticated users to access other projects' task runs by UID. Attackers with permission on one project can supply foreign task or task run UIDs to read execution logs, database session details, and rollback SQL from other projects.
Weakness: CWE-639
Which versions are affected by CVE-2026-115322?
How do I fix CVE-2026-115322?
No fix has been published for CVE-2026-115322 yet. Limit exposure of the affected software until one is available.
Is CVE-2026-115322 being exploited?
There is no known exploitation of CVE-2026-115322 in the wild and no public exploit code.
Sources
Also known as GHSA-4vfr-m29p-8gpj.