dbcli mycli up to 2.29.4/2.30.1 Whitelist source.py source_special_command_is_safe os command injection
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.0 | $0-$5k | 1.42+ |
Summary
A vulnerability was found in dbcli mycli up to 2.29.4/2.30.1. It has been classified as problematic. This affects the function source_special_command_is_safe of the file mycli/packages/special/source.py of the component Whitelist. The manipulation leads to os command injection.
This vulnerability is uniquely identified as CVE-2026-116053. Local access is required to approach this attack. Moreover, an exploit is present.
The vendor was contacted early about this disclosure but did not respond in any way.
Details
A vulnerability was found in dbcli mycli up to 2.29.4/2.30.1 and classified as problematic. This issue affects the function source_special_command_is_safe of the file mycli/packages/special/source.py of the component Whitelist. The manipulation with an unknown input leads to a os command injection vulnerability. Using CWE to declare the problem leads to CWE-78. The product constructs all or part of an OS command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended OS command when it is sent to a downstream component. Impacted is confidentiality, integrity, and availability.
The identification of this vulnerability is CVE-2026-116053. The exploitation is known to be easy. An attack has to be approached locally. Technical details as well as a public exploit are known. MITRE ATT&CK project uses the attack technique T1202 for this issue.
It is declared as proof-of-concept. The vendor was contacted early about this disclosure but did not respond in any way.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.3VulDB Meta Temp Score: 5.0
VulDB Base Score: 5.3
VulDB Temp Score: 5.0
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Os command injectionCWE: CWE-78 / CWE-77 / CWE-74
CAPEC: 🔒
ATT&CK: 🔒
Physical: Partially
Local: Yes
Remote: No
Availability: 🔒
Access: Public
Status: Proof-of-Concept
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Timeline
10/24/2026 Advisory disclosed10/24/2026 VulDB entry created
10/24/2026 VulDB entry last update
Sources
Status: ConfirmedCVE: CVE-2026-116053 (🔒)
GCVE (CVE): GCVE-0-2026-116053
GCVE (VulDB): GCVE-100-426137
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 10/24/2026 23:29Changes: 10/24/2026 23:29 (54)
Complete: 🔍
Cache ID: 216::103
Submit
Accepted
- Submit #995818: dbcli mycli v2.25.3/ main @ b57e676 (as of 2026-09-23) mycli/packages/special/source.py whitelist asymmetry → persisten (by github.com)
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.