Loading vulnerability…
In MarkUs prior to 2.9.1, the assignment configuration import endpoint (courses/<:course_id>/assignments/upload_config_files) allows instructors to upload a ZIP archive to create an assignment from an exported configuration. The application uses ZIP entry names to construct filesystem paths and writes files to disk without validating or sanitizing those paths. A crafted ZIP containing traversal sequences (e.g., ../) can cause files to be written outside the intended extraction directory (a Zip Slip/path traversal during archive extraction). This issue is fixed in MarkUs 2.9.1.
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.
This two-file repository is an operational proof of concept for CVE-2026-25057, an authenticated path-traversal flaw in MarkUs assignment configuration ZIP uploads. README.md documents the affected versions, instructor upload workflow, and Git-over-SSH trigger. poc.py is a Python 3 ZIP generator that packages required benign assignment configuration fixtures and appends a malicious archive member with five parent-directory traversals. The default member path targets MarkUs's lib/repo/markus-git-shell.sh and writes a Bash reverse shell that calls 127.0.0.1:8080. The payload name and payload content are command-line configurable, allowing alternative write targets and commands. Successful exploitation requires instructor credentials, a vulnerable ZIP extraction implementation, and sufficient application filesystem permissions. The repository does not include the referenced MarkUs fixture files, so its default mode requires a MarkUs source checkout adjacent to the script (or a user-supplied --fixtures directory); otherwise it exits before producing an archive. The default loopback callback also requires payload customization for a remote listener in typical deployments.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
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.