# CVE-2026-45432: Cleartext Transmission of Credentials Vulnerability in GX Earth ONT Models

> Remote attackers can intercept plaintext credentials from the web interface to gain unauthorized access to GX Earth ONT devices.

- **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:** 4 Jun 2026
- **Updated:** 4 Jun 2026
- **Also known as:** GHSA-4jr5-8v5x-7499

## What is CVE-2026-45432?

CVE-2026-45432 is a high-severity vulnerability in GX Earth 1010, published on 4 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

This vulnerability exists in GX Earth ONT models due to the transmission of user credentials in plaintext over HTTP in its web management interface. A remote attacker could exploit this vulnerability by intercepting network traffic to obtain sensitive authentication information, which could lead to unauthorized access to the targeted device.

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

## Which versions are affected by CVE-2026-45432?


## How do I fix CVE-2026-45432?

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

## Is CVE-2026-45432 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-45432 and fix it if it is affected.

What it is: CVE-2026-45432 is a high-severity vulnerability in GX Earth 1010, published on 4 Jun 2026. 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-2026-45432 in the wild and no public exploit code.

Affected product: GX Earth 1010. 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-2026-45432/ (Markdown: https://insights.sbomify.com/CVE-2026-45432/index.md)
```

## Sources

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

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