CVE-2026-25732 affects NiceGUI, a Python-based UI framework. In versions prior to 3.7.0, the FileUpload.name property exposes client-supplied filename metadata without sanitization. When application code uses common patterns such as constructing a destination path with UPLOAD_DIR / file.name, an attacker can supply filenames containing traversal sequences such as ../ to escape the intended upload directory. The issue is therefore a path traversal leading to arbitrary file write in applications that incorporate file.name into filesystem paths without sanitization. The vulnerability is described as a design footgun rather than an unconditional framework-level arbitrary write: applications that use fixed paths, generated filenames, or explicit sanitization are not affected. In vulnerable deployment patterns, arbitrary file overwrite may enable remote code execution, for example by overwriting application files that are later executed or loaded.
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.
FileUpload.name. Sanitize filenames by stripping directory components, for example with Path(e.file.name).name, or preferably generate server-side random filenames. As a defense-in-depth measure, enforce a base-directory constraint when saving uploads by resolving the target path and rejecting any resolved path that escapes the intended upload root.1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos (1 hidden).
Repository contains a single Python exploit script and a README describing CVE-2026-25732 (NiceGUI <= 3.6.1) path traversal in FileUpload leading to unauthenticated arbitrary file write. Structure: - README.md: Vulnerability description, affected/fixed versions, impact examples, and sample command lines showing traversal/overwrite targets. - exploit_cve_2026_25732.py: Standalone Python3 script using requests to send a multipart/form-data POST to the provided target URL (normalized to end with '/'). It sets the uploaded part name to attacker-controlled 'malicious_filename' (the key primitive) and the content to bytes read from a local payload file. Exploit capabilities: - Remote, unauthenticated arbitrary file write via path traversal/absolute path in the uploaded filename (FileUpload.name) when the server-side app uses that name in its save path without sanitization. - Potential follow-on impact depends on what is written: overwriting app.py/main.py for code execution on restart/reload, writing to system/user config locations, or dropping web-accessible files if applicable. Network behavior / targeting: - Performs a single HTTP POST (no auth, no session handling) to the base target URL (commonly the NiceGUI app root '/'), with multipart field 'file'. - Reports status codes and prints a snippet of the response body; no automatic verification of file write beyond HTTP response heuristics. Notable assumptions/limitations: - Assumes the upload endpoint is the page itself (POST to '/'); real deployments may use a different route depending on app configuration. - Success requires the NiceGUI process to have filesystem write permissions to the chosen destination path and the vulnerable filename handling pattern in the app code.
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.
5 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.