# CVE-2026-116053: dbcli mycli Whitelist source.py source_special_command_is_safe os command injection


- **Severity:** Medium 4.8 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 25 Oct 2026
- **Updated:** 26 Oct 2026
- **Also known as:** DEBIAN-CVE-2026-116053, GHSA-hw4q-9p72-mrfx

## What is CVE-2026-116053?

CVE-2026-116053 is a medium-severity vulnerability in dbcli mycli, published on 25 Oct 2026. 

### Official description

A weakness has been identified in dbcli mycli up to 2.29.4/2.30.1. The impacted element is the function source_special_command_is_safe of the file mycli/packages/special/source.py of the component Whitelist. Executing a manipulation can lead to os command injection. It is possible to launch the attack on the local host. The exploit has been made available to the public and could be used for attacks. The vendor was contacted early about this disclosure but did not respond in any way.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command), CWE-77 (Improper Neutralization of Special Elements used in a Command)

## Which versions are affected by CVE-2026-116053?


## How do I fix CVE-2026-116053?

No fix has been published for CVE-2026-116053 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-116053 being exploited?

There is no known exploitation of CVE-2026-116053 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-116053 and fix it if it is affected.

What it is: CVE-2026-116053 is a medium-severity vulnerability in dbcli mycli, published on 25 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-116053 in the wild and no public exploit code.

Affected product: dbcli mycli. 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-116053/ (Markdown: https://insights.sbomify.com/CVE-2026-116053/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-116053
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-116053
- OSV: https://osv.dev/vulnerability/CVE-2026-116053

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-116053/
Summaries are generated and may contain mistakes; the official description above is the record.