VulnerabilityPublished 5 Sep 2025

CVE-2025-55671: kujirahand TkEasyGUI · Uncontrolled Search Path Element

Affects kujirahand TkEasyGUISource CVE Database V5

Not known to be exploited · CVSS 7.8 High : upgrade to 1.0.22 soon.

Data as of 26 Oct 2026, 11:42 UTC

CVSS 3.0 base score

7.8High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.1% chance of exploitation in 30 days – higher than 5% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 1.0.22

CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Attack Vector: Local
Attack Complexity: Low
Privileges Required: None
User Interaction: Required
Scope: Unchanged
Confidentiality: High
Integrity: High
Availability: High

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Local: The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either: the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or remotely (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., tricking a legitimate user into opening a malicious document).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation 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 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade kujirahand TkEasyGUI to 1.0.22.

Affected software

Product	Affected	Fixed in
kujirahand TkEasyGUI	Affected <1.0.22	Fixed in 1.0.22

AI-suggested

Immediate upgrade to TkEasyGUI version 1.0.22 or later once the patch is officially released, as this is the definitive fix for the vulnerability.
Until patching is possible, restrict local access to systems running vulnerable versions of TkEasyGUI to trusted users only, minimizing the risk of local exploitation.
Implement application whitelisting and execution control policies to prevent unauthorized or unexpected executables from running in directories included in the search path.
Educate users about the risks of running untrusted applications or opening suspicious files that might trigger the vulnerability via user interaction.
Conduct thorough audits of systems to identify all instances of TkEasyGUI and verify their versions.
Monitor logs and endpoint detection systems for unusual activity that could indicate exploitation attempts, such as unexpected process launches or privilege escalations.
Employ least privilege principles to limit the permissions of users running TkEasyGUI, reducing the potential impact of code execution.
Review and harden environment variables and system PATH settings to prevent insertion of malicious directories that could be exploited by this vulnerability.

Description

Uncontrolled search path element issue exists in TkEasyGUI versions prior to v1.0.22. If this vulnerability is exploited, arbitrary code may be executed with the privilege of running the program.

Impact

For European organizations, the impact of CVE-2025-55671 can be significant, especially for those relying on TkEasyGUI in internal tools or applications. Since the vulnerability allows arbitrary code execution with the privileges of the running user, an attacker who gains local access could execute malicious code, potentially leading to data breaches, system compromise, or lateral movement within the network. The requirement for local access and user interaction somewhat limits remote exploitation but does not eliminate risk, particularly in environments where users might be tricked into opening malicious files or running compromised applications. Confidentiality, integrity, and availability of sensitive data and systems could be severely affected. Organizations in sectors with high regulatory requirements (e.g., finance, healthcare, critical infrastructure) may face compliance issues if exploited. Additionally, the vulnerability could be leveraged in targeted attacks or insider threat scenarios. Given the high impact on all three security pillars, European organizations should prioritize identification and remediation of affected systems to prevent exploitation.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 5 Sep 2025, 13:53 UTC

Technical details

References

Community reviews

Related threats