CVE-2025-55037: kujirahand TkEasyGUI · OS Command Injection
Affects kujirahand TkEasyGUISource CVE Database V5
Not known to be exploited · CVSS 9.8 Critical : upgrade to 1.0.22 as a priority.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 2.3% chance of exploitation in 30 days – higher than 83% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 1.0.22
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 5 Sep 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.
What to do
Upgrade kujirahand TkEasyGUI to 1.0.22.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| kujirahand TkEasyGUI | Affected
| Fixed in
|
AI-suggested
1. Immediate upgrade to TkEasyGUI version 1.0.22 or later, where the vulnerability is patched, is the most effective mitigation. 2. If upgrading is not immediately possible, implement strict input validation and sanitization on all external inputs used to construct OS commands within applications using TkEasyGUI. 3. Employ application-level whitelisting to restrict allowable commands or parameters passed to the OS shell. 4. Use OS-level security controls such as running TkEasyGUI processes with the least privilege necessary to limit the impact of potential exploitation. 5. Monitor logs and network traffic for unusual command execution patterns or unexpected outbound connections that may indicate exploitation attempts. 6. Employ network segmentation to isolate vulnerable systems and reduce attack surface. 7. Consider using application firewalls or runtime application self-protection (RASP) solutions that can detect and block command injection attempts. 8. Conduct code reviews and security testing on applications using TkEasyGUI to identify and remediate insecure command construction practices. 9. Educate developers and system administrators about the risks of command injection and secure coding practices.
Description
Improper neutralization of special elements used in an OS command ('OS Command Injection') issue exists in TkEasyGUI versions prior to v1.0.22. If this vulnerability is exploited, an arbitrary OS command may be executed by a remote unauthenticated attacker if the settings are configured to construct messages from external sources.