Loading vulnerability…
CVE-2025-54368 affects uv, a Python package and project manager written in Rust. In uv 0.8.5 and earlier, remote ZIP archives were processed in a streaming manner and file entries were not reconciled with the ZIP archive central directory. This allowed specially crafted ZIP archives to present different effective contents to different package installers. The advisory specifically describes two cases: ZIP archives containing multiple local file entries that could appear legitimate to some installers while yielding malicious contents to others, and "stacked" ZIP inputs containing multiple internal ZIPs that different installers would interpret differently. The attacker could choose which installer behavior to target. The issue was corrected in uv 0.8.6.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
Repository contains a single Python exploit script (mass-regist.py) plus a short README. The script is a mass-targeting WordPress exploit aimed at the “SF Booking” plugin (README cites CVE-2025-54368). It normalizes target URLs, uses a requests.Session with SSL verification disabled, rotates User-Agent strings, and runs concurrently via ThreadPoolExecutor for scanning/exploitation at scale. Core behavior: for each target, it fetches a page expected to contain a signup/registration nonce, extracts the nonce using multiple regex patterns (get_nonce_signup), then submits a registration payload (generate_user_data) using hardcoded EMAIL/PASSWORD (operator is instructed to edit these). The payload includes role-related fields (e.g., provider-role: package_0) consistent with attempting to abuse a plugin registration workflow to obtain elevated privileges. It also includes a WordPress REST API check to /wp-json/wp/v2/users as a basic fingerprint/validation step. Outputs: writes a run log to registration.log and saves per-target results to success.txt/failed.txt; when successful it also records credentials in credentials.txt. Overall, this is an operational mass exploitation tool (not just detection) focused on creating accounts and attempting admin-level access via a vulnerable WordPress plugin registration mechanism.
4 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.