CVE-2025-6810: Mescius ActiveReports.NET · Deserialization of Untrusted Data
Affects Mescius ActiveReports.NETSource CVE Database V5
Not known to be exploited · CVSS 9.8 Critical.
Data as of 26 Oct 2026, 06:26 UTC
- EPSS
- 0.8% chance of exploitation in 30 days – higher than 59% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 7 Jul 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
NuGetMescius/activereports.netpkg:nuget/Mescius/activereports.netOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
1. Immediate upgrade: Organizations should promptly update to a patched version of Mescius ActiveReports.NET once it becomes available. 2. Input validation: Until a patch is available, implement strict input validation and sanitization on all data passed to the ReadValue method or any deserialization routines involving ActiveReports.NET. Reject or sanitize any untrusted serialized data. 3. Network segmentation: Restrict network access to services using ActiveReports.NET to trusted internal networks only, minimizing exposure to external attackers. 4. Application hardening: Employ application-level controls such as sandboxing or running the reporting service with least privilege to limit the impact of potential exploitation. 5. Monitoring and detection: Deploy intrusion detection/prevention systems and monitor logs for unusual deserialization activity or unexpected process behavior related to ActiveReports.NET components. 6. Incident response readiness: Prepare to respond quickly to any signs of exploitation by having forensic and remediation plans in place. 7. Vendor engagement: Engage with Mescius support to obtain early patches or mitigation guidance and report any suspicious activity.
Description
Mescius ActiveReports.NET ReadValue Deserialization of Untrusted Data Remote Code Execution Vulnerability. This vulnerability allows remote attackers to execute arbitrary code on affected installations of Mescius ActiveReports.NET. Interaction with this library is required to exploit this vulnerability but attack vectors may vary depending on the implementation. The specific flaw exists within the implementation of the ReadValue method. The issue results from the lack of proper validation of user-supplied data, which can result in deserialization of untrusted data. An attacker can leverage this vulnerability to execute code in the context of the current process. Was ZDI-CAN-25246.