Skip to main content
VulnerabilityPublished Updated

CVE-2025-34143: ETQ Reliance CG (legacy) · Authentication Bypass Using an Alternate Path or Channel

Affects ETQ Reliance CG (legacy)Source CVE Database V5

0

Not known to be exploited · public detection template (Nuclei) · 38% EPSS · CVSS 9.3 Critical.

Data as of 26 Oct 2026, 09:15 UTC

CVSS 4.0 base score
9.3Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
38.0% chance of exploitation in 30 days – higher than 98% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 22 Jul 2025

  2. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  3. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  4. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
ETQ Reliance CG (legacy)Affected
  • =0
Fixed in–

AI-suggested

A fix is available in ETQ Reliance CG (legacy) version MP-4583, which introduces stricter validation to exclude internal SYSTEM accounts from public authentication workflows. Users of affected versions should upgrade to MP-4583 or later to remediate this vulnerability. No cloud service remediation applies as this is not a cloud-hosted product. Patch status is confirmed by the vendor advisory embedded in the description.

Description

An authentication bypass vulnerability exists in ETQ Reliance on the CG (legacy) platform. The application allowed login as the privileged internal SYSTEM user by manipulating the username field. The SYSTEM account does not require a password, enabling attackers with network access to the login page to obtain elevated access. Once authenticated, an attacker could achieve remote code execution by modifying Jython scripts within the application. This issue was resolved by introducing stricter validation logic to exclude internal accounts from public authentication workflows in version MP-4583.

References

Community reviews

Loading reviews…