Bytebase DBHub read-only mode bypass in keyword blacklist
- Exploited
- No known exploitation
- Fix
- See vendor advisory
- Who is exposed
- Not reported
Summary
Bytebase DBHub contains a flaw in its Read Only Mode, where an incomplete blacklist in the escapeHatchFunctionKeywords function lets crafted input in the tool argument get past the read-only restriction. An attacker can reach it remotely over the network, but needs a low-privilege login, and the vendor did not respond when contacted about the issue.
Written by a model
Original description
A security vulnerability has been detected in Bytebase DBHub up to 2.0.0. Impacted is the function escapeHatchFunctionKeywords of the file src/utils/allowed-keywords.ts of the component Read Only Mode. The manipulation of the argument tool leads to incomplete blacklist. Remote exploitation of the attack is possible. The vendor was contacted early about this disclosure but did not respond in any way.
What to do
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-133964 (Bytebase DBHub Read Only Mode allowed-keywords.ts escapeHatchFunctionKeywords incomplete blacklist), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-133964 (entry last updated 2026-11-21):
Affected:
- Bytebase DBHub: versions 2.0
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-133964 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-133964 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://vuldb.com/vuln/441546
- https://vuldb.com/vuln/441546/cti
- https://vuldb.com/cve/CVE-2026-133964
- https://vuldb.com/submit/1052007
- https://github.com/bytebase/dbhub/security/advisories/GHSA-69r3-848g-rpx6
- https://github.com/bytebase/dbhub/
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-133964
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-133964"}.Affected versions
- Bytebase DBHub2.0
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure3/25Reachable over the network · Unknown: No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity5.3/10CVSS 5.3
- No patch5/5No fixed version listed; see vendor advisory
What would change the score
- Would score about 68 if added to CISA KEV
- Would score about 63 if CISA's SSVC rates exploitation active
- Would score about 32 if advisories confirm default setups are exposed
Timeline
- CVE published
- First seen by cve.now
Evidence 8
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | GitHub · bytebase/dbhub · Advisory GHSA-69r3-848g-rpx6 |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-133964 |
| Record | NVD · CVE-2026-133964 |
| Other links 5 | |
| Advisory | VulDB · Advisory #441546 |
| Advisory | VulDB · Threat intelligence #441546 |
| Advisory | VulDB · CVE-2026-133964 record |
| Advisory | VulDB · Submission #1052007 |
| Repository | GitHub · bytebase/dbhub · Repository |
Questions about CVE-2026-133964
Is CVE-2026-133964 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.
Source: cve.now feed data
Which versions are affected by CVE-2026-133964?
DBHub: version 2.0.
Source: cve.now feed data
Related
- CVE-2026-61742DBHub HTTP transport DNS rebinding allows unauthenticated browser-origin SQL execution
- CVE-2026-61788@bytebase/dbhub's read-only mode does not prevent database writes
- CVE-2026-61789DBHub: MySQL and MariaDB comment interpretation bypasses read-only SQL validation
- CVE-2022-51026Bytebase 0.12.0 before 1.0.1 Authentication Bypass via GitLab Self-Hosted Login
- CVE-2026-115322Bytebase before 3.16.0 Authorization Bypass via Rollout Service Task Run Handlers
- CVE-2026-115321Bytebase before 3.16.0 Authorization Bypass via UpdateIssueComment
No corrections so far. Something wrong on this page? Report an error.