# CVE-2025-62765: General Industrial Controls Lynx+ Gateway Cleartext Transmission of Sensitive Information

> An attacker can observe network traffic to obtain sensitive information, including plaintext credentials, from the General Industrial Controls Lynx+ Gateway.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Nov 2025
- **Updated:** 17 Nov 2025
- **Also known as:** GHSA-9g9v-vcmw-4mp4

## What is CVE-2025-62765?

CVE-2025-62765 is a high-severity vulnerability in General Industrial Controls Lynx+ Gateway, published on 14 Nov 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

General Industrial Controls Lynx+ Gateway is vulnerable to a cleartext transmission vulnerability that could allow
 an attacker to observe network traffic to obtain sensitive information,
 including plaintext credentials.

Weakness: CWE-319 (Cleartext Transmission of Sensitive Information)

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


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

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

## Is CVE-2025-62765 being exploited?

There is no known exploitation of CVE-2025-62765 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2025-62765 is a high-severity vulnerability in General Industrial Controls Lynx+ Gateway, published on 14 Nov 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-62765 in the wild and no public exploit code.

Affected product: General Industrial Controls Lynx+ Gateway. 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-62765/ (Markdown: https://insights.sbomify.com/CVE-2025-62765/index.md)
```

## Sources

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

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