Loading vulnerability…
CVE-2025-40629 is a directory traversal vulnerability in PNETLab 4.2.10 caused by improper sanitization of user-supplied input in the application's file access mechanisms. By manipulating file path values in HTTP requests, an attacker can cause the application to access files outside the intended directory boundary. The issue stems from insufficient validation or canonicalization of path input before it is used in file operations, enabling traversal sequences to reach sensitive files on the underlying system.
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 repository contains a single Python script (CVE-2025-40629.py) that exploits an authenticated path traversal vulnerability (CVE-2025-40629) in PNETLab. The script is a standalone exploit that requires valid credentials (default admin/pnet) to authenticate to the target PNETLab instance. It then locates a valid lab, crafts a malicious request to the /api/export endpoint with a path traversal payload, and downloads a ZIP file containing the requested file from the server's filesystem. The script extracts and displays (or saves) the file content. The code is well-structured, with clear separation of authentication, exploitation, and file extraction logic. The main attack vector is network-based, targeting HTTP endpoints on the PNETLab server. The endpoints /store/public/auth/login/login, /api/folders, and especially /api/export are fingerprintable and central to the exploit's operation. The exploit is operational, providing a working file read primitive but not a full weaponized framework.
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.
2 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.