High · CVSS 7.5CVE-2026-103098

GV-Eye Sensitive information exposure in URL query parameter Vulnerability

Answer in brief

CVE-2026-103098 records a High severity (CVSS 7.5) vulnerability in GV-Eye Sensitive information exposure in URL query parameter Vulnerability. The current sources do not mark it as known exploited. The current feed maps GeoVision Inc./GV-Eye (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Oct 2, 2026Updated Oct 2, 2026Source checked Oct 2, 2026First seen by HOL Oct 2, 2026Material review Oct 2, 2026

Upstream Advisory

Key facts

Risk: High · CVSS 7.5
Exploitation: Not marked as known exploited
Affected software: 1 mapped package or product
Fix availability: Not reported

Why this deserves its current priority

CVSS is 7.5. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps GeoVision Inc./GV-Eye (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
GeoVision Inc./GV-Eyegeneric	V3.6.0	Not reported

Recommended response

Check inventory. Check lockfiles and deployed manifests for GeoVision Inc./GV-Eye.
Review the reported fix. Monitor this advisory for an available fix and review any installs of the affected package.

Evidence timeline and material changes

Published upstream
Oct 2, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Oct 2, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Oct 2, 2026

Sources and claim methodology

Source referencegeovision.com.tw

Upstream source description

Transmission of a sensitive key in the URL over an unencrypted HTTP connection. The request is sent over HTTP rather than HTTPS, meaning the key is transmitted in plaintext across the network. An attacker with the ability to monitor network traffic could intercept the request and obtain the key

Quoted source text, attributed separately from HOL analysis.