What is the CVSS score of CVE-2026-25925?

CVE-2026-25925 has a CVSS 3.1 base score of 7.8 (High). CVSS vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H. EPSS exploitation probability: 0.0%.

Is there a public PoC exploit available for CVE-2026-25925?

Yes, a public proof-of-concept exploit is available for CVE-2026-25925. Prioritise patching immediately. EPSS: 0.0%.

How to fix or mitigate CVE-2026-25925?

Within 24 hours: Identify all systems running PowerDocu versions prior to 2.4.0 and isolate them from production environments if feasible. Within 7 days: Restrict PowerDocu access to trusted users only, disable JSON import features if possible, and monitor for suspicious Flow/App package submissions. Within 30 days: Upgrade to PowerDocu 2.4.0 or later once patches are released, or migrate to alternative documentation solutions if upgrade timeline is unclear.

Powerdocu CVE-2026-25925

HIGH

Deserialization of Untrusted Data (CWE-502)

2026-02-09 security-advisories@github.com

Windows .NET Powerdocu

7.8

CVSS 3.1 · GitHub Advisory

View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

Access

Craft malicious JSON file with arbitrary $type property
Delivery

User opens Flow/App package in PowerDocu
Exploit

Application deserializes untrusted JSON
Execution

Arbitrary .NET object instantiation
Impact

Remote code execution

Vulnerability Assessment

Weakness	CWE CWE-502 OWASP Top 10:2025 A08:2025 - Software or Data Integrity Failures ASVS 5.0 V1 - Encoding and Sanitization Safe deserialization, type allowlists MITRE ATT&CK 2 techniques across 2 tactics: Execution, Initial Access The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. Sign in to read
Exploitation Conditions	PowerDocu versions prior to 2.4.0 processing Flow or App packages containing JSON files with malicious $type properties. User interaction required to open the package.
Impact	CVSS 7.8 (HIGH). Attack vector: Local. Complexity: Low. Privileges required: None. User interaction: Required. Public exploit/POC available.
Exploit ScenarioDerived	An attacker could exploit this vulnerability to compromise the affected system.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).

No patch listed yet 0.0% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Mar 12, 2026

PowerDocu versions prior to 2.4.0 allow arbitrary .NET object instantiation and code execution through unsafe deserialization of the $type property in JSON files within Flow or App packages. A local attacker with user interaction can exploit this vulnerability to achieve full system compromise. Public exploit code exists for this vulnerability, and no patch is currently available for affected versions.

Earlier versions of this analysis (1)

v1 Mar 12, 2026 - 21:54 CVSS 7.8

RemediationAI

Fixed in version 2.4.0..

Affects your stack

Find out whether the stacks and servers you run are on an affected version.

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

Classified as CWE-502 (Deserialization of Untrusted Data). Affects Powerdocu. PowerDocu contains a Windows GUI executable to perform technical documentations. Prior to 2.4.0, PowerDocu contains a critical security vulnerability in how it parses JSON files within Flow or App packages. The application blindly trusts the $type property in JSON files, allowing an attacker to instantiate arbitrary .NET objects and execute code. This vulnerability is fixed in 2.4.0.

Know when Powerdocu gets its next vulnerability

Watch products and get an email when something new is published
Check this CVE against your own stack and servers
Exploit and PoC references, threat intelligence from 22 sources

Continue with Google Continue with GitHub

No credit card · 7-day full trial

Severity by source

GitHub Advisory PRIMARY 7.8 HIGH

AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Primary rating from GitHub Advisory · only source for this CVE.

CVSS VectorGitHub Advisory

Attack Vector

Local

Attack Complexity

Low

Privileges Required

None

User Interaction

Required

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Lifecycle Timeline

PoC Detected

Feb 28, 2026 - 00:13 vuln.today

Public exploit code

CVE Published

Feb 09, 2026 - 22:16 nvd

HIGH 7.8

DescriptionGitHub Advisory

PowerDocu contains a Windows GUI executable to perform technical documentations. Prior to 2.4.0, PowerDocu contains a critical security vulnerability in how it parses JSON files within Flow or App packages. The application blindly trusts the $type property in JSON files, allowing an attacker to instantiate arbitrary .NET objects and execute code. This vulnerability is fixed in 2.4.0.

Executive ViewAI

Why It Matters

PowerDocu versions prior to 2.4.0 contain a critical vulnerability that allows attackers to exploit JSON file parsing in Flow and App packages, potentially leading to unauthorized access or system compromise. Organizations using PowerDocu for documentation automation should immediately assess exposure and restrict access until remediation is available.

Business Impact: High

Compensating Controls

Disable JSON import and Flow/App package parsing features in PowerDocu if not business-critical. Implement network segmentation to restrict PowerDocu system access from untrusted sources. Monitor and validate all Flow and App package files before processing through PowerDocu. Implement application whitelisting on systems running PowerDocu. Establish an air-gapped environment for PowerDocu operations if possible. Monitor vendor communications for patch availability and schedule immediate deployment upon release.

Threat Intelligence Overview

EPSS Score

0.0%

Top 93% exploitable

Exploit

POC

Public exploit code exists

Data Quality

4 sources

Confidence: Medium

NVD

CVE.org

EPSS

GitHub

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue

Severity HIGH

CISA KEV No

Public POC Yes

EPSS 0.0%

Patch available No

Active threat No

Deciding rule

HIGH severity (CVSS 7.0-8.9)

What every action level means

Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.

Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.

This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.

This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.

Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.