{"answers":{"affected":"3 open source packages ship an affected version, including pip.","exploited":"There is no known exploitation of CVE-2026-6357 in the wild and no public exploit code.","fix":"Upgrade pip to 26.1 or later.","what":"CVE-2026-6357 is a medium-severity code injection vulnerability in pip, published on 27 Apr 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-6357 and fix it if it is affected.\n\nWhat it is: CVE-2026-6357 is a medium-severity code injection vulnerability in pip, published on 27 Apr 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-6357 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- pip (PyPI): affected all versions; fixed in 26.1\n- pip (PyPI): affected all versions; fixed in 26.1\n- pip (PyPI): affected all versions; fixed in 26.1\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-6357/ (Markdown: https://insights.sbomify.com/CVE-2026-6357/index.md)","id":"CVE-2026-6357","markdown":"https://insights.sbomify.com/CVE-2026-6357/index.md","name":"CVE-2026-6357","record":{"aliases":["AZL-85011","AZL-85265","BELL-CVE-2026-6357","CLEANSTART-2026-SE54902","CLEANSTART-2026-ZI04041","DEBIAN-CVE-2026-6357","ECHO-0a2a-4462-0b2a","GHSA-jp4c-xjxw-mgf9","MINI-24m3-7gvf-6572","MINI-4hq9-rm2j-67f4","MINI-4mv4-xw4q-9v7m","MINI-6vpf-gp4x-w56q","MINI-834f-55f7-x32g","MINI-83jr-f9qp-7vm5","MINI-crx3-vx3p-2mfx","MINI-gx8f-ffch-hwf8","MINI-v92g-j3vg-2jfp","PYSEC-2026-2876","ROOT-APP-PYPI-CVE-2026-6357","UBUNTU-CVE-2026-6357"],"analysis":{"component_type":"developer_tool","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Python package installer","requires_auth":"high_privilege","summary":"Attackers can execute arbitrary code by installing malicious wheels that are imported during pip's self-update check before the update completes.","user_interaction":"required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"PSF","cpe":[],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:L/AC:L/AT:P/PR:H/UI:A/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-829","name":"Inclusion of Functionality from Untrusted Control Sphere"}],"description":"pip prior to version 26.1 would run self-update check functionality after installing wheel files which required importing well-known Python modules names. These module imports were intentionally deferred to increase startup time of the pip CLI. The patch changes self-update functionality to run before wheels are installed to prevent newly-installed modules from being imported shortly after the installation of a wheel package. Users should still review package contents prior to installation.","ecosystems":["PyPI"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"pip self-update functionality can import newly installed modules after wheel installation","id":"CVE-2026-6357","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"code_injection","year":"2026"},"n_packages":3,"n_references":2,"next":{"headline":"Use after free in Chrome","id":"CVE-2026-6358"},"packages":[{"ecosystem":"PyPI","fixed":["26.1"],"introduced":["0"],"last_affected":[],"package":"pip","purl":null,"source":"GHSA-jp4c-xjxw-mgf9"},{"ecosystem":"PyPI","fixed":["26.1"],"introduced":["0"],"last_affected":[],"package":"pip","purl":"pkg:pypi/pip","source":"GHSA-jp4c-xjxw-mgf9"},{"ecosystem":"PyPI","fixed":["26.1"],"introduced":["0"],"last_affected":[],"package":"pip","purl":"pkg:pypi/pip","source":"PYSEC-2026-2876"}],"prev":{"headline":"CVE-2026-6356","id":"CVE-2026-6356"},"products":["pip"],"published":"2026-04-27","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"PyPA Advisory Database","prefix":"PYSEC"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-04-27","vendors":["Pip maintainers"]},"summary":"Attackers can execute arbitrary code by installing malicious wheels that are imported during pip's self-update check before the update completes.","url":"https://insights.sbomify.com/CVE-2026-6357/"}