# CVE-2025-34140: ETQ Reliance CG/NXG API Authorization Bypass via ;localized-text URI Suffix

> Unauthenticated attackers can bypass authorization checks via URI suffix manipulation to access sensitive data in ETQ Reliance platforms.

- **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:** 22 Jul 2025
- **Updated:** 28 Jul 2026
- **Also known as:** GHSA-8j4g-7p6h-w548

## What is CVE-2025-34140?

CVE-2025-34140 is a high-severity authentication bypass vulnerability in ETQ Reliance CG (legacy), published on 22 Jul 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An authorization bypass vulnerability exists in ETQ Reliance (legacy CG and NXG SaaS platforms). By appending a specific URI suffix to certain API endpoints, an unauthenticated attacker can bypass access control checks and retrieve limited sensitive resources. The root cause was a misconfiguration in API authorization logic, which has since been corrected in SE.2025.1 and 2025.1.2.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

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


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

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

## Is CVE-2025-34140 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-34140 is a high-severity authentication bypass vulnerability in ETQ Reliance CG (legacy), published on 22 Jul 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-34140 in the wild and no public exploit code.

Affected product: ETQ Reliance CG (legacy). 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-34140/ (Markdown: https://insights.sbomify.com/CVE-2025-34140/index.md)
```

## Sources

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

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