Loading story…
Python disclosed CVE-2026-5271, a medium-severity flaw in the Python install manager that affects script alias entrypoints generated by version 26.0. The bug could leave the search path empty, allowing a Python module in the current working directory to override the intended module and execute code as the user. Python said the issue is fixed in version 26.1, noted that versions prior to 26.0 are not affected, and advised users to update and regenerate vulnerable aliases with:
py install --refresh
A separate medium-severity issue, CVE-2026-3219, was disclosed in pip for its handling of concatenated TAR and ZIP archives. pip treated concatenated TAR/ZIP files as ZIP archives regardless of filename or whether the file could be interpreted as both formats, creating confusing installation results and potentially installing files that did not match the expected archive type. The fix changes pip so installation proceeds only when an archive is uniquely identified as either ZIP or TAR, reducing the risk of ambiguous package handling in Python software distribution workflows.
See real exploitation activity before you spend the cycle.
4 events from the most recent confirmed update back to the earliest known activity.
The announced fix for CVE-2026-3219 changes pip so installation proceeds only when a file is uniquely identified as either a ZIP archive or a tar archive, but not both. This addressed confusing installation outcomes caused by ambiguous archive parsing.
Python disclosed CVE-2026-3219, a medium-severity vulnerability in pip's handling of concatenated tar and ZIP archives. Pip could treat concatenated tar and ZIP files as ZIP files regardless of filename, potentially causing installation of files that did not match the expected archive type.
Python stated that install manager version 26.1 fixes CVE-2026-5271, while versions prior to 26.0 are not affected. Users were advised to update and run "py install --refresh" to regenerate aliases created by the vulnerable release.
Python disclosed CVE-2026-5271, a medium-severity vulnerability in version 26.0 of the Python install manager. The flaw could leave the search path empty for generated script alias entrypoints, allowing a module in the current working directory to override the intended module and execute code as the user.
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
See real exploitation activity behind this advisory so you can triage it against everything else in the queue.
2 references tracked. Mallory keeps watching after this page renders.
seclists.org
Open sourceseclists.org
Open sourceMap indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.
Other stories Mallory is tracking that overlap on entities, sources, or topic labels.
GitPython has disclosed seven vulnerabilities affecting multiple versions of the widely used Python library, exposing CI/CD and other automation environments to supply-chain risk. The most severe issue, **CVE-2026-73625** (`CVSS 8.8`), allows remote code execution by bypassing `check_unsafe_options` and smuggling unsafe Git options through crafted keyword arguments, enabling arbitrary command execution through parameters such as `--upload-pack`. Affected methods include `clone_from`, `fetch`, `pull`, `push`, `ls_remote`, `iter_commits`, `blame`, and `archive`, according to public advisories and CVE records. The broader disclosure also includes **CVE-2026-73622**, which can leak secrets by expanding environment variables in attacker-controlled URLs and writing them into `.git/config` or `.gitmodules`, as well as **CVE-2026-73620** and **CVE-2026-73624**, which permit arbitrary file read or overwrite through unsafe option forwarding in functions such as `IndexFile.checkout()`, `TagReference.create()`, and `Diffable.diff()`. GitHub advisories further describe related issues involving local file disclosure, git-directory creation outside the destination, unsafe configuration handling, and hook or template abuse. Fixes were released across versions **3.1.54**, **3.1.55**, **3.1.56**, and **3.1.57**, with reports indicating that upgrading to **GitPython 3.1.57** remediates all seven CVEs; no active exploitation was reported at publication time.
Aug 14, 2026
CPython disclosed two medium-severity vulnerabilities affecting distinct parts of the runtime and tooling. **CVE-2026-1502** allows CR/LF bytes to pass through HTTP client proxy tunnel header or host handling, creating a header-injection risk in proxy tunnel scenarios. The issue was published through Python security channels and the `oss-sec` mailing list, with remediation details tracked in the CVE record and an associated CPython pull request. A second flaw, **CVE-2026-5713**, affects CPython remote debugging and introspection features and can trigger out-of-bounds read and write behavior when a privileged Python process connects to a malicious or compromised Python target. The bug impacts newer capabilities including `profiling.sampling` in Python 3.15+ and asyncio inspection commands such as ``` python -m asyncio ps python -m asyncio pstree ``` in Python 3.14+, and exploitation is expected to be unstable because the connecting process is likely to crash under ASLR.
Jun 29, 2026
The Python Software Foundation disclosed a **critical authentication bypass** in the `python.org` release management API that could have let attackers forge administrator-level requests and modify Python release metadata. The flaw, reported by Splitline Ng of DEVCORE and confirmed by the Python Security Response Team, could have enabled changes to download and verification URLs for official Python installers, creating a path to distribute tampered files through trusted `python.org` infrastructure. The vulnerable logic reportedly dated back to 2014, affecting the release pipeline for more than a decade, but maintainers said post-incident forensics found **no evidence of exploitation**. The PSF patched the issue rapidly, with production fixes deployed within 24 hours and broader remediation completed within 48 hours, while also disabling risky API behavior and tightening release controls. Additional hardening included stricter URL validation, mandatory HTTPS enforcement, negative authentication test coverage, longer log retention, and stronger provenance measures around release artifacts, including emphasis on **Sigstore** alongside existing **PGP** signing. A subsequent Trail of Bits review funded by OpenAI reportedly found no additional authentication or authorization flaws, and the Foundation said the changes were designed to reduce the risk of unauthorized modification of Python downloads distributed via official channels.
Jul 12, 2026