CVE-2026-133964 json
Bytebase DBHub Read Only Mode allowed-keywords.ts escapeHatchFunctionKeywords incomplete blacklist
published 18h ago modified 17h ago also EUVD-2026-132066
- cvss
- 5.3
- version 4.0, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.6%
- EPSS 0.6% chance of exploitation in 30 days, percentile 46%
- public exploits
- 0
- none known
Summary
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.
Is CVE-2026-133964 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
0.55% chance of exploitation in the next 30 days, higher than 46% of all scored CVEs (FIRST EPSS, 2026-11-21).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 4.0 | 5.3 | CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:X |
| CNA | 3.1 | 6.3 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L/E:X/RL:X/RC:C |
| CNA | 3.0 | 6.3 | CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L/E:X/RL:X/RC:C |
| CNA | 2.0 | 6.5 | AV:N/AC:L/Au:S/C:P/I:P/A:P/E:ND/RL:ND/RC:C |
| NVD | 3.1 | 6.3 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L |
Affected products
- Bytebase DBHub
Classification
References
-
vuldb.com
/vuln/441546
vdb-entry, technical-description
-
vuldb.com
/vuln/441546/cti
signature, permissions-required
-
vuldb.com
/cve/CVE-2026-133964
third-party-advisory
-
vuldb.com
/submit/1052007
third-party-advisory
-
github.com
/bytebase/dbhub/security/advisories/GHSA-69r3-848g-rpx6
broken-link
-
github.com
/bytebase/dbhub/
product
Sources
- CVE List CVE-2026-133964
- NVD CVE-2026-133964
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.