CVE-2025-27590 affects oxidized-web (Oxidized Web) before version 0.15.0. The vulnerability is in the RANCID migration page, which is exposed in a way that allows an unauthenticated user to gain control over the Linux user account under which oxidized-web is running. Based on the available description, the issue stems from missing authentication protection on functionality intended to perform or assist with RANCID migration, enabling unauthorized access to privileged application behavior.
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 proof-of-concept (PoC) exploit for CVE-2025-27590, a command injection vulnerability in web applications that process multipart file uploads insecurely. The exploit is implemented in Python (exploit.py) and targets a /migration HTTP endpoint on the victim server. It crafts a multipart/form-data POST request with malicious payloads in the 'cloginrc' and 'file1' form parts, exploiting improper sanitization to execute arbitrary shell commands. The default payload injects an SSH public key into the target's ~/.ssh/authorized_keys file, granting the attacker SSH access. The exploit is configurable via command-line arguments for the target host, port, and file path to write to. The repository also includes a README.md with detailed usage instructions and a summary of the vulnerability. No detection scripts or framework integration are present; this is a standalone PoC exploit.
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.