CVE-2026-114109 astral-sh CVE debrief

Who should care

Developers and administrators using uv for package management should assess exposure and upgrade to uv 0.11.15 or later. They should also monitor for suspicious activity and consider compensating controls. This includes reviewing and updating affected packages, and tracking exceptions and retesting remediated assets. The vulnerability can lead to potential code execution under malicious wheel control, shadow or overwrite existing executables, and result in

Why it matters

CVE-2026-114109 allows a malicious wheel to write files outside the intended environment, potentially leading to code execution or unexpected behavior. Defenders should upgrade to uv 0.11.15 or later and monitor for suspicious activity.

• Potential code execution under malicious wheel control
• Shadow or overwrite existing executables
• Unexpected behavior from installed packages

Technical summary

In versions of uv prior to 0.11.15, a malicious wheel could use entry point specifications to place an executable outside of the intended environment, potentially shadowing or overwriting existing executables. This vulnerability allows a malicious wheel to write files outside the intended environment, potentially leading to code execution or unexpected behavior. The vulnerability can be addressed by upgrading to uv 0.11.15 or later. Defenders should assess exposure and monitor for suspicious activity. The vulnerability affects developers and administrators using uv for package management.

Defensive priority

Upgrade to uv 0.11.15 or later to address arbitrary file write vulnerability

Recommended defensive actions

• Upgrade to uv 0.11.15 or later
• Review and update affected packages
• Monitor for suspicious wheel installations
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
• Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance
• Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed
• Check relevant monitoring, detection, and logs for exposed assets that need extra review

Evidence notes

The vulnerability allows a malicious wheel to place an executable outside of the intended environment, potentially shadowing or overwriting existing executables. This requires the target to install a malicious wheel.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.