VulnerabilityPublished 4 Nov 2025

CVE-2025-56230: Tencent Docs Desktop · Missing Validation of OpenSSL Certificate

Source CVE Database V5

Not known to be exploited · CVSS 7.5 High.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score

7.5High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 13% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 4 Nov 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 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

AI-suggested

Immediately restrict network access to Tencent Docs update servers using firewall rules or network segmentation to limit exposure to potential MITM attacks.
Monitor network traffic for unusual or unauthorized connections to update endpoints, employing SSL/TLS inspection where feasible to detect anomalies.
Disable automatic updates in Tencent Docs Desktop until a verified patch is released, and perform manual updates only from trusted sources.
Employ endpoint security solutions capable of detecting tampered or malicious update payloads.
Educate IT and security teams on the risks associated with missing SSL validation and ensure incident response plans include scenarios involving compromised update mechanisms.
Once patches are available, prioritize their deployment across all affected systems.
Consider using network-level protections such as DNS filtering or proxy servers that enforce strict certificate validation policies.
Conduct regular audits of software update mechanisms for all critical applications to detect similar weaknesses proactively.

Description

Tencent Docs Desktop 3.9.20 and earlier suffers from Missing SSL Certificate Validation in the update component.

Impact

For European organizations, the missing SSL certificate validation in Tencent Docs Desktop’s update component could lead to severe confidentiality breaches. Attackers could intercept or manipulate update traffic to inject malicious code, potentially compromising the entire application and exposing sensitive corporate documents. This risk is heightened in sectors relying heavily on cloud collaboration tools, such as finance, legal, and government agencies. The vulnerability could also undermine trust in software supply chains, leading to broader operational disruptions. Given that the vulnerability requires no privileges or user interaction, it can be exploited remotely by attackers with network access, increasing the threat scope. Organizations using Tencent Docs Desktop without proper network segmentation or monitoring may face increased risk of espionage or data leakage. Additionally, the absence of a patch at the time of disclosure means organizations must rely on interim mitigations, which may not fully eliminate the risk. The impact on confidentiality could have regulatory implications under GDPR if personal or sensitive data is exposed.

CWE-599Missing Validation of OpenSSL Certificate (opens in a new tab)
Variant weakness
The product uses OpenSSL and trusts or uses a certificate without using the SSL_get_verify_result() function to ensure that the certificate satisfies all necessary security requirements.
Architecture and Design
Ensure that proper authentication is included in the system design.
Implementation
Understand and properly implement all checks necessary to ensure the identity of entities involved in encrypted communications.
OWASP ASVS 4.0.3
V2.8.5 (opens in a new tab)
V2.8.4 (opens in a new tab)
V9.2.3 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

notion.so/CVE-2025-56230-1a74e9f2a40d80dca0a2d0615dc7ac5a (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 4 Nov 2025, 22:09 UTC

WeaknessesCWE-599

Technical details

References

Community reviews

Related threats