# CVE-2025-65083: Security feature bypass in GoSign Desktop

> GoSign Desktop disables TLS certificate validation when using a proxy, allowing integrity protection bypass in specific non-default configurations.

- **Severity:** Low 3.2 (`CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:C/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Nov 2025
- **Updated:** 17 Nov 2025
- **Also known as:** GHSA-j3r3-q9v5-gg3h

## What is CVE-2025-65083?

CVE-2025-65083 is a low-severity vulnerability in Tinexta Infocert GoSign Desktop, published on 17 Nov 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

GoSign Desktop through 2.4.1 disables TLS certificate validation when configured to use a proxy server. This can be problematic if the GoSign Desktop user selects an arbitrary proxy server without consideration of whether outbound HTTPS connections from the proxy server to Internet servers succeed even for untrusted or invalid server certificates. In this scenario (which is outside of the product's design objectives), integrity protection could be bypassed. In typical cases of a proxy server for outbound HTTPS traffic from an enterprise, those connections would not succeed. (Admittedly, the usual expectation is that a client application is configured to trust an enterprise CA and does not set SSL_VERIFY_NONE.) Also, it is of course unsafe to place ~/.gosign in the home directory of an untrusted user and then have other users execute downloaded files.

Weakness: CWE-295 (Improper Certificate Validation)

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


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

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

## Is CVE-2025-65083 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-65083 is a low-severity vulnerability in Tinexta Infocert GoSign Desktop, published on 17 Nov 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-65083 exists.

Affected product: Tinexta Infocert GoSign Desktop. 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-65083/ (Markdown: https://insights.sbomify.com/CVE-2025-65083/index.md)
```

## Sources

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

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