{"items":[{"id":"NVI-00010762","kind":"vulnerability","title":"uv vulnerable to arbitrary file deletion through RECORD entries","revision":2,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-pjjw-68hj-v9mw","CVE-2026-114110"],"plain_summary":"GitHub lists this reviewed advisory for uv. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-77608fd0d9ed24609a029295c5a6e4e5"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[{"kind":"EPSS","as_of":"2026-10-31T12:00:27.000Z","value":"0.348%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.28397. Missing scores are unknown.","source_id":"sr-77608fd0d9ed24609a029295c5a6e4e5"}],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-f0bd3ad2bd7167584dfc866c35fc335f","url":"https://github.com/advisories/GHSA-pjjw-68hj-v9mw","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-pjjw-68hj-v9mw","publisher":"GitHub Advisory Database","observed_at":"2026-10-31T22:07:08.657Z"},{"id":"sr-77608fd0d9ed24609a029295c5a6e4e5","url":"https://www.first.org/epss/data.html","basis":"official_catalog","notes":"FIRST EPSS; probability of exploitation in the next 30 days, not local compromise. Dataset date/model retained; FIRST services terms apply.","title":"CVE-2026-114110","publisher":"FIRST EPSS","observed_at":"2026-10-31T23:13:27.688Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-f0bd3ad2bd7167584dfc866c35fc335f"],"technology":"uv","known_exclusions":[],"conditions_summary":"## Impact\n\nWheel RECORD entries can contain relative paths that traverse outside of the wheel’s installation prefix. In versions 0.11.5 and earlier of uv, these wheels were not rejected on installation and the RECORD was respected without validation on uninstall.\n\nuv uses the RECORD to determine files to remove on uninstall. Consequently, a malicious or malformed wheel could induce deletion of arbitrary files outside of the wheel’s installation prefix on uninstall.\n\nuv does not use the RECORD file to determine wheel file paths. Invalid RECORD entries cannot be used to create or modify files in arbitrary locations.\n\nStandards-compliant Python packaging tooling does not produce RECORD files that exhibit this behavior; an attacker must manually manipulate the RECORD. A user must install *and* uninstall the malformed wheel to be affected. An attack must guess the depth of the installation prefix path in order to target system files.\n\nAbsolute paths in RECORD files are not allowed by the specification and, when present, uv always treats them as rooted in the wheel’s installation prefix. Absolute paths cannot be used to delete arbitrary files.\n\nOnly files can be deleted, attempts to dele","public_affected_ranges":["<= 0.11.5"]}],"null_published_at":"2026-11-03T10:03:21.812Z","source_updated_at":"2026-10-23T20:58:15.000Z","source_disclosed_at":"2026-04-10T19:39:15.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"Dated EPSS estimate updated; this is not a new disclosure or proof of exploitation.","null_first_observed_at":"2026-10-31T22:07:08.657Z"},{"id":"NVI-00010762","kind":"vulnerability","title":"uv vulnerable to arbitrary file deletion through RECORD entries","revision":1,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-pjjw-68hj-v9mw","CVE-2026-114110"],"plain_summary":"GitHub lists this reviewed advisory for uv. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-f0bd3ad2bd7167584dfc866c35fc335f"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-f0bd3ad2bd7167584dfc866c35fc335f","url":"https://github.com/advisories/GHSA-pjjw-68hj-v9mw","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-pjjw-68hj-v9mw","publisher":"GitHub Advisory Database","observed_at":"2026-10-31T22:07:08.657Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-f0bd3ad2bd7167584dfc866c35fc335f"],"technology":"uv","known_exclusions":[],"conditions_summary":"## Impact\n\nWheel RECORD entries can contain relative paths that traverse outside of the wheel’s installation prefix. In versions 0.11.5 and earlier of uv, these wheels were not rejected on installation and the RECORD was respected without validation on uninstall.\n\nuv uses the RECORD to determine files to remove on uninstall. Consequently, a malicious or malformed wheel could induce deletion of arbitrary files outside of the wheel’s installation prefix on uninstall.\n\nuv does not use the RECORD file to determine wheel file paths. Invalid RECORD entries cannot be used to create or modify files in arbitrary locations.\n\nStandards-compliant Python packaging tooling does not produce RECORD files that exhibit this behavior; an attacker must manually manipulate the RECORD. A user must install *and* uninstall the malformed wheel to be affected. An attack must guess the depth of the installation prefix path in order to target system files.\n\nAbsolute paths in RECORD files are not allowed by the specification and, when present, uv always treats them as rooted in the wheel’s installation prefix. Absolute paths cannot be used to delete arbitrary files.\n\nOnly files can be deleted, attempts to dele","public_affected_ranges":["<= 0.11.5"]}],"null_published_at":"2026-10-31T22:27:12.381Z","source_updated_at":"2026-10-23T20:58:15.000Z","source_disclosed_at":"2026-04-10T19:39:15.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"First indexed by Null; source disclosure date is shown separately.","null_first_observed_at":"2026-10-31T22:07:08.657Z"}],"next_cursor":null,"snapshot_revision":"42594"}