Astral uv CVE-2026-114109

Requires the victim to install a specifically crafted malicious wheel using uv prior to 0.11.15; the wheel must declare a console_scripts or gui_scripts entry point whose name contains path-traversal components so the generated executable lands outside the environment's scripts directory in a PATH directory. This is default uv behavior (no special configuration needed), but exploitation is limited by the requirement that the attacker first convince the target to install the untrusted wheel and that the installed uv version is below 0.11.15; there is no workaround other than upgrading.

This is a genuine but conditional risk rather than a drop-everything remote threat. The provided CVSS 4.0 score of 8.7 (High) rests on AV:N/AC:L/PR:N/UI:N, but this conflicts with the advisory text: exploitation explicitly requires that 'the attacker must induce their target into installing a malicious wheel,' which is meaningful user interaction and a supply-chain/social-engineering precondition the UI:N metric ignores. The scored impact (VC:H, VI:N, VA:N) is also questionable - the vulnerability is an arbitrary file write that shadows or overwrites executables on PATH, so the direct impact is integrity leading to code execution, not confidentiality. No EPSS score, CISA KEV listing, or public exploit was provided in the intelligence, so there is no public exploit identified at time of analysis and no evidence of active exploitation. Net assessment: a widely-used developer tool with a high-impact flaw, but exploitation depends on tricking a victim into installing an attacker-controlled package, which lowers real-world likelihood versus a true unauthenticated network RCE. Treat as a high-priority patch for developer/CI fleets, but recognize the attack is gated behind package-trust decisions rather than being internet-sprayable.

An attacker publishes a malicious wheel (e.g., a typosquatted or dependency-confusion package) whose console_scripts or gui_scripts entry point name embeds path-traversal sequences. When a victim installs it using uv before 0.11.15, the generated executable is written outside the environment's scripts directory into a PATH directory, shadowing or overwriting a legitimate binary so the attacker's code runs the next time that command is invoked. No public exploit was identified in the provided data.