PatchTheCVECVE-2026-116053: A weakness has been identified in dbcli mycli up to 2.29.4/2.30.1
CVE-2026-116053 is a medium-severity flaw (CVSS 5.3) affecting affected software. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
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 discl
Why this priority
- No elevated risk signals yet
No fix is published yet: follow the downgrade or mitigation steps.
Last updated 2026-10-25 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score
Timeline
- Published CVE record published
- Updated Record last modified
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.
Quick answers
How do I fix CVE-2026-116053?
No fixed release is listed yet. Watch the vendor advisory and apply any mitigation shown on this page.
Is CVE-2026-116053 being exploited?
CVE-2026-116053 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.
What does CVE-2026-116053 affect?
CVE-2026-116053 affects affected software. Severity is medium (CVSS 5.3). 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 lea
How urgent is CVE-2026-116053?
Priority 19/100. No elevated risk signals yet.