# CVE-2025-56230: Security feature bypass in n/a

> Attackers can bypass SSL validation in the update component to deliver malicious updates, potentially leading to code execution.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Nov 2025
- **Updated:** 4 Nov 2025
- **Also known as:** GHSA-ph8v-q2pj-5pg4

## What is CVE-2025-56230?

CVE-2025-56230 is a high-severity vulnerability in n/a, published on 4 Nov 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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

Weakness: CWE-599 (Missing Validation of OpenSSL Certificate)

## Which versions are affected by CVE-2025-56230?

It affects 1 product.


Products: Tencent Docs.

## How do I fix CVE-2025-56230?

No fix has been published for CVE-2025-56230 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-56230 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-56230 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-56230 and fix it if it is affected.

What it is: CVE-2025-56230 is a high-severity vulnerability in n/a, published on 4 Nov 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-56230 exists.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-56230/ (Markdown: https://insights.sbomify.com/CVE-2025-56230/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-56230
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-56230
- OSV: https://osv.dev/vulnerability/CVE-2025-56230

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-56230/
Summaries are generated and may contain mistakes; the official description above is the record.