Skip to main content
VulnerabilityPublished

CVE-2025-6811: Mescius ActiveReports.NET · Deserialization of Untrusted Data

Affects Mescius ActiveReports.NETSource CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.0 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
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:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 7 Jul 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
NuGetmescius/activereports.netpkg:nuget/mescius/activereports.netOther threatsAffected
  • =18.1.1
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Immediate mitigation steps should include: 1) Conducting an inventory to identify all applications and services using Mescius ActiveReports.NET version 18.1.1. 2) Applying any available patches or updates from Mescius as soon as they are released. 3) If patches are not yet available, consider temporarily disabling or isolating services that utilize the vulnerable component, especially those exposed to untrusted networks or users. 4) Implement strict input validation and sanitization on all serialized data inputs to prevent untrusted data deserialization. 5) Employ application-layer firewalls or intrusion prevention systems to monitor and block suspicious serialized payloads targeting the TypeResolutionService. 6) Review and harden application permissions to limit the impact of potential code execution. 7) Monitor logs and network traffic for unusual activity indicative of exploitation attempts. 8) Engage with software vendors and security communities for updates and exploit intelligence. These measures go beyond generic advice by focusing on the specific vulnerable component and its integration context.

Description

Mescius ActiveReports.NET TypeResolutionService 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 TypeResolutionService class. 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-25397.

References

Community reviews

Loading reviews…