Loading vulnerability…
CVE-2025-26014 is a remote code execution vulnerability affecting Loggrove version 1.0. Based on the provided information, the flaw is reachable via the path parameter, which allows a remote attacker to execute arbitrary code. The available context does not identify the specific vulnerable function or code path, but the issue is consistent with unsafe handling of externally supplied input in a way that results in code execution.
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 working exploit for CVE-2025-26014, a remote code execution (RCE) vulnerability in Loggrove v1.0. The main exploit file ('exploit') is a Python script that automates the attack process. It first logs into the Loggrove web interface using default credentials (admin:loggrove), checks for or creates a log file, and then exploits a command injection vulnerability in the 'path' parameter of the 'read.py' endpoint. The exploit delivers a reverse shell payload, either via Python or netcat, to the attacker's specified listener and port. The repository also includes a README (with a screenshot) and a 'docker-requirements' file describing the environment setup for testing. The exploit is operational, providing a real reverse shell if the target is vulnerable and accessible. The attack vector is network-based, targeting the HTTP interface of Loggrove. The only code file is the exploit script, which is self-contained and does not rely on any external exploit 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.