CVE-2026-114110 astral-sh CVE debrief

Who should care

Defenders responsible for managing uv installations and ensuring the integrity of package installations should be aware of this vulnerability and take steps to verify and patch their installations.

Why it matters

CVE-2026-114110 is a vulnerability in the uv package that allows for arbitrary file deletion through RECORD entries. Defenders should prioritize verifying the integrity of uv installations and ensuring that all RECORD entries are validated and sanitized.

• Verification of uv package integrity is required to prevent arbitrary file deletion.
• Defenders must ensure that RECORD entries are validated and sanitized to prevent exploitation.
• uv installations must be patched to version 0.11.6 or later to fix the vulnerability.
• Monitoring of uv installations for suspicious activity is recommended to detect potential exploitation attempts.

Technical summary

The vulnerability is caused by uv's failure to reject wheels with relative paths in RECORD entries that traverse outside of the wheel's installation prefix. The RECORD file is used to determine files to remove on uninstall. An attacker must manually manipulate the RECORD file to exploit this vulnerability. This vulnerability can lead to the deletion of arbitrary files outside of the wheel's installation prefix on uninstall. To mitigate this vulnerability, defenders should prioritize verifying the integrity of uv installations and ensuring that all RECORD entries are validated and sanitized.

Defensive priority

Defenders should prioritize verifying the integrity of uv installations and ensuring that all RECORD entries are validated and sanitized.

Recommended defensive actions

• Verify the integrity of uv installations and ensure that all RECORD entries are validated and sanitized.
• Ensure that all uv packages are up-to-date and patched to version 0.11.6 or later.
• Monitor uv installations for suspicious activity and implement compensating controls to prevent arbitrary file deletion.
• Review compensating controls for exposed systems while remediation is scheduled and verified.
• Check relevant monitoring, detection, and logs for exposed assets that need extra review.
• Track exceptions, retest remediated assets, and close the item only after evidence is documented.
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up.

Evidence notes

The vulnerability is caused by uv's failure to reject wheels with relative paths in RECORD entries that traverse outside of the wheel's installation prefix. The RECORD file is used to determine files to remove on uninstall.

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.