Loading story…
A high-severity vulnerability tracked as CVE-2026-53951 affects the Copier library and CLI, allowing attackers to bypass the tool’s template trust protections and trigger execution of template-defined actions without the usual --trust prompt. The flaw impacts versions 9.5.0 through 9.15.1 and stems from improper validation of trusted template URLs: Copier checked trust with a raw str.startswith comparison before normalizing the path, enabling a crafted template reference containing .. to appear to match a trusted prefix while resolving to a different, attacker-controlled location.
Successful exploitation can cause Copier to run malicious tasks, migrations, or jinja_extensions, resulting in arbitrary command execution with potential impact to confidentiality, integrity, and availability. The issue is classified under CWE-22 and CWE-94, and the project has released Copier v9.15.2 to fix the trust-bypass path traversal issue; the release notes identify the update as a security fix preventing trusted template URL abuse.
See affected versions and whether adversaries are exploiting it.
2 events from the most recent confirmed update back to the earliest known activity.
CVE-2026-53951 was disclosed as a vulnerability in the Copier library and CLI application, caused by a raw prefix check before URL normalization that allows path traversal to bypass trust prompts. The issue can let attacker-controlled templates execute tasks, migrations, or Jinja extensions without the normal --trust confirmation, leading to arbitrary command execution.
The copier-org project released Copier version 9.15.2, including a security fix to prevent a trust bypass via path traversal in trusted template URLs. This patch addresses the flaw affecting versions 9.5.0 through 9.15.1.
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
See whether adversaries are exploiting this yet, and where the affected versions run in your environment.
2 references tracked. Mallory keeps watching after this page renders.
Map 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.
Multiple newly disclosed vulnerabilities exposed **arbitrary file write** paths through symlink handling and path validation failures in developer and server-side software. In **Crawl4AI** before `0.8.8`, `CVE-2026-56258` affects screenshot and PDF endpoints by combining weak `output_path` validation, symlink following, and a **TOCTOU** race, allowing unauthenticated remote attackers to write files outside the intended directory and potentially reach code execution. In **Cursor Desktop** before `3.0`, `CVE-2026-50549` lets a malicious agent escape the workspace sandbox by forcing path canonicalization to fail and then abusing an in-workspace symlink to write arbitrary files under the user’s privileges, including paths that could enable later unsandboxed execution. A related pattern also appeared in archive extraction and privileged upload handling. The **extract-zip** package is affected by `CVE-2026-56876`, which fails to validate symlink targets inside ZIP archives, enabling path traversal outside the extraction directory and possible arbitrary file read or write when processing untrusted archives. Separately, **pwnlift** disclosed `CVE-2026-56815` in a privileged upload handler that could be abused for arbitrary file write **as root** through direct symlink following and a TOCTOU race; an initial fix was bypassable before a follow-up patch was merged, while one downstream deployment mitigated exposure by removing the privileged `sudo` entry. Together, the disclosures highlight recurring risk from incomplete path canonicalization, unsafe symlink handling, and containment checks in file-write workflows.
Jul 2, 2026
Paperclip, an open-source control plane for AI agent teams, patched a **critical authorization bypass** tracked as `CVE-2026-41679` that could let a remote attacker self-register on exposed instances, obtain board-level API access, and execute arbitrary commands on the host running the service. The issue affected network-accessible deployments using Paperclip’s default authenticated-mode configuration, where missing authorization checks allowed an attacker to create and approve a CLI challenge, gain a persistent credential, and abuse a company import path that should have been restricted to instance administrators. By importing a crafted `.paperclip.yaml` file, an attacker could define an agent and command that would be executed by a host-level adapter with the permissions of the Paperclip server process. Paperclip also fixed two additional flaws reported by Oasis Security: `GHSA-x8hx-rhr2-9rf7`, a DNS rebinding issue in default `local_trusted` mode that could enable local command execution on developer machines, and `GHSA-xfqj-r5qw-8g4j`, which exposed issue data, skill documentation, and deployment details through missing authentication and authorization checks on several API routes. The fixes were released in source tag **`v2026.416.0`**, and operators were advised to upgrade to that version or later. Public exploit code has increased risk, including a Rapid7 Metasploit module for `CVE-2026-41679`, while reporting cited proof-of-concept exploitation but no confirmed active exploitation in the wild at the time of publication.
Aug 6, 2026
CERT Polska disclosed three vulnerabilities in **GNU cpio** affecting versions through **2.15**, tracked as `CVE-2026-66484`, `CVE-2026-66485`, and `CVE-2026-66486`. The issues were reported by researchers from the **AFINE Team** and fixed in upstream commits. The most serious flaw allows **path traversal** during archive extraction, a weakness aligned with `CWE-22`, in which crafted file paths can escape the intended extraction directory and potentially overwrite or access files outside the restricted path. The additional bugs include an **uncontrolled memory allocation** issue mapped to `CWE-789` that can trigger a **stack overflow** and denial of service, and an **improper output escaping** flaw that can produce forged archive listings or inject terminal escape sequences. Together, the vulnerabilities expose users handling untrusted archives to file-system compromise, service disruption, and deceptive terminal output, underscoring the risk of insufficient pathname validation, unsafe memory handling, and unescaped archive metadata in command-line archive tools.
Aug 10, 2026