LiveActive security incident?Get immediate response
CVE Record

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

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.

HighCVSS 8.7Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

ETQ Reliance legacy CG and NXG SaaS could expose limited sensitive API resources to an unauthenticated internet attacker. A specially formed request can avoid an authorization check. The supplied CVSS 4.0 score is 8.7, reflecting potentially serious confidentiality loss without credentials or user interaction. No integrity or availability impact is identified.

Executive priority

Treat this as a high-priority confidentiality issue. Quickly identify affected ETQ environments, confirm SaaS tenant status, and restrict exposed APIs where correction cannot be verified. Escalate if Reliance stores regulated, quality, safety, or commercially sensitive records. The available evidence does not justify claiming an active exploitation emergency.

Technical view

CVE-2025-34140 is a network-reachable API authorization bypass caused by misconfigured authorization logic. Appending a particular URI suffix to certain endpoints can permit unauthenticated retrieval of limited sensitive resources. The issue is categorized as CWE-639. The source bundle states the correction is included in CG SE.2025.1 and NXG 2025.1.2.

Likely exposure

Organizations using legacy Reliance CG before SE.2025.1 or Reliance NXG SaaS before 2025.1.2 may be exposed, especially where affected APIs are externally reachable. Exact endpoints, data types, and deployment prerequisites are not identified in the supplied evidence. NXG customers should verify their tenant release with ETQ.

Exploitation context

Exploitation requires network access but no credentials, user interaction, or elevated complexity according to the supplied CVSS vector. The source bundle does not establish active exploitation, and the CVE is not identified as being in CISA KEV. Public proof-of-concept availability is not established by the provided information.

Researcher notes

The supplied CVSS 4.0 vector is AV:N/AC:L/AT:N/PR:N/UI:N with high vulnerable-system confidentiality impact and no stated integrity, availability, or subsequent-system impact. Exact affected endpoints and retrievable resource classes remain unspecified. Version-range notation in the bundle is ambiguous, but its narrative explicitly names SE.2025.1 and 2025.1.2 as corrected releases.

Mitigation direction

  • Upgrade Reliance CG to SE.2025.1 or a later vendor-supported release.
  • Confirm Reliance NXG SaaS is running 2025.1.2 or later.
  • Restrict external API access until the corrected release is verified.
  • Review ETQ's security update for deployment-specific instructions and exceptions.

Validation and detection

  • Inventory Reliance CG and NXG deployments, tenant releases, and exposed API interfaces.
  • Confirm installed or hosted versions against ETQ's corrected release levels.
  • Review access logs for unauthenticated requests containing unusual URI suffix patterns.
  • Verify affected API resources reject unauthenticated access after remediation.
  • Coordinate safe validation with ETQ because affected endpoints are not specified here.
Prepared
Confidence
high
Sources
4

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-639: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Privilege behavior lookup

The CVE wording references privilege impact, so privilege escalation and authorization behavior review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2025-34140 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
8.7 (4.0)
Known Exploited
No
Published

Vector: 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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
3Timeline events
1ADP providers
4Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: yesTechnical Impact: partial

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
8.7CVSS 4.0HighCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N——VulnCheck

Vulnerability scoring details

Base CVSS 4.0 score

8.7High
CVSS 4.0 vector shape for CVE-2025-34140Attack VectorAttack ComplexityAttack RequirementsPrivileges RequiredUser InteractionVS ConfidentialityVS IntegrityVS AvailabilitySS ConfidentialitySS IntegritySS Availability

Vector: 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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Attack Requirements
NonePresent
Privileges Required
NoneLowHigh
User Interaction
NonePassiveActive
VS Confidentiality
HighLowNone
VS Integrity
HighLowNone
VS Availability
HighLowNone
SS Confidentiality
HighLowNone
SS Integrity
HighLowNone
SS Availability
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
ETQReliance CG (legacy)0, SE.2025.1unaffected
ETQReliance NXG (SaaS)0, 2025.1.2unaffected
Weakness

CWE details

CWE-639

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-639 · source CWE mapping

Authorization Bypass Through User-Controlled Key

Authorization Bypass Through User-Controlled Key represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.

Open CWE intelligenceSame-CWE CVEs