# CVE-2025-34142: ETQ Reliance CG < SE.2025.1 / < 2025.1.2 XXE Injection in SSO SAML Handler


- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:N/SC:L/SI:L/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 22 Jul 2025
- **Updated:** 15 May 2026
- **Also known as:** GHSA-v8jr-7g4w-cp39

## What is CVE-2025-34142?

CVE-2025-34142 is a medium-severity vulnerability in ETQ Reliance CG (legacy), published on 22 Jul 2025. 

### Official description

An XML External Entity (XXE) injection vulnerability exists in ETQ Reliance on the CG (legacy) platform within the `/resources/sessions/sso` endpoint. The SAML authentication handler processes XML input without disabling external entity resolution, allowing crafted SAML responses to invoke external entity references. This could enable attackers to retrieve sensitive files or perform server-side request forgery (SSRF). The issue was addressed by disabling external entity processing for the affected XML parser in versions SE.2025.1 and 2025.1.2.

Weakness: CWE-611 (Improper Restriction of XML External Entity Reference)

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


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

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

## Is CVE-2025-34142 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-34142 is a medium-severity vulnerability in ETQ Reliance CG (legacy), published on 22 Jul 2025. 
Exploitation: There is no known exploitation of CVE-2025-34142 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-34142/ (Markdown: https://insights.sbomify.com/CVE-2025-34142/index.md)
```

## Sources

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

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