CVE REMEDIATION GUIDE
Review reviewHighResearch in progress

CVE-2026-45431 remediation guide

GX INDIA GX Earth 2022, GX Earth 1010

This vulnerability exists in GX Earth ONT models due to improper handling of user-supplied input in multiple diagnostic functions in its web management interface. An authenticated remote attacker could exploit this vulnerability by injecting arbitrary and executing OS commands on the targeted device. Successful exploitation of this vulnerability could allow the attacker to perform remote code execution with root privileges on the targeted device.

Open CVE record
Research in progress

A verified fixed-version field is not available. Use the linked NVD and supporting references, then confirm the vendor-supported path before changing production systems.

ProductGX INDIA GX Earth 2022, GX Earth 1010
Affected versions>= version E2022 - 3.1.2A, >= version E2022 - 3.1.5AV, >= version E2022 - 1.1ASL, >= version E1010-1.1ASL
Fixed versionsNo verified fixed-version field is available yet
Priority basisReview · CVSS 8.7 · EPSS 0.39%
01

Identify the affected asset

Confirm whether GX INDIA GX Earth 2022, GX Earth 1010 is installed, record the deployed version and installation path, and identify exposed interfaces.

  • Record the product name, package or appliance identifier, and installed version.
  • Identify internet-facing, administrative, API, and internal access paths.
  • Preserve the pre-change configuration and relevant service logs.
02

Validate the affected-version match

Compare the deployed version with the affected range: >= version E2022 - 3.1.2A, >= version E2022 - 3.1.5AV, >= version E2022 - 1.1ASL, >= version E1010-1.1ASL. Treat incomplete inventory results as unresolved.

03

Prioritize with independent signals

The CVSS severity warrants an early asset and exposure review. Combine this signal with asset criticality, exposure, compensating controls, and business impact.

04

Apply supported remediation

Follow the vendor advisory or supported update path. Current fixed-version status: No verified fixed-version field is available yet. Preserve configuration and rollback material before change.

05

Verify the result

Confirm the resulting version, service health, authentication and access paths, monitoring coverage, and relevant security logs.

  • Confirm the expected version and package state.
  • Run a functional health check for critical service paths.
  • Review authentication, error, application, and security monitoring logs.
  • Reassess exposure if the supported fix cannot be applied.

Operational boundary

This page does not replace the vendor advisory, support contract, change-management process, or recovery plan. Do not infer that an asset is unaffected from an incomplete inventory query or a missing fixed-version field.