thefuck CVE-2026-95168

Exploitation requires local access and the ability to place or modify a Python rule file within a directory enumerated by get_rules_import_paths (thefuck's user/contrib rules import paths); the malicious code runs when the victim next invokes thefuck and Rule.from_path imports the file. Limiting factors: the attacker must already have a local foothold (AV:L) and write permission to a rules path, and code executes only with the privileges of the user running thefuck - meaningful privilege escalation requires a higher-privileged user to run thefuck against an attacker-writable path. No authentication beyond the low-privilege local account (PR:L) is required, and there is no network exposure. Affected version is thefuck v3.32; no fixed version is identified in the available data.

CVSS 3.1 base score is 7.8 (High) with vector AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, indicating a locally-exploitable code-injection flaw (CWE-94) that requires low privileges but yields full confidentiality, integrity and availability impact. All exploitation signals point toward LOW real-world urgency despite the High CVSS: EPSS is only 0.16% (5th percentile), the CVE is NOT on CISA KEV, and there is no evidence of active exploitation. The MITRE references include a third-party vulnerability report (REYu6/python-vuln, '03-contrib-pregate-exec.md') and the upstream issue #1623, which suggests proof-of-concept/analysis material is publicly documented, but no weaponized or in-the-wild exploit is confirmed. The local attack vector (AV:L) is the dominant mitigating factor - an attacker already needs a foothold on the host, so this is an execution-in-context/escalation primitive rather than a remotely wormable threat. Net assessment: a legitimate but lower-priority issue for most environments, mattering most where thefuck runs in shared or privileged contexts. Note the CPE is a placeholder (cpe:2.3:a:n/a:n/a:*) and affected-version data is 'n/a', so automated matching against asset inventories will fail - verify the affected build (v3.32) manually.

A local attacker who can write to one of thefuck's rule import paths (e.g. a user or contrib rules directory) plants a malicious Python rule file. When a victim subsequently runs the fuck command, thefuck enumerates paths via get_rules_import_paths and loads each rule through Rule.from_path, importing and executing the attacker-controlled code with the victim's privileges. A public vulnerability report referencing this behavior exists, and the local, low-complexity nature (AV:L/AC:L) makes exploitation reliable once write access to a rules path is obtained.