Skip to main content

CVE-2026-103097: CWE-798: Use of Hard-coded Credentials in GeoVision Inc. GV-Eye

0
High
VulnerabilityCVE-2026-103097cvecve-2026-103097cwe-798cwe-540cwe-312
Published: 10/02/2026 (10/02/2026, 00:14:46 UTC)
Source: CVE Database V5
Vendor/Project: GeoVision Inc.
Product: GV-Eye

Description

CVE-2026-103097 is a vulnerability in GeoVision Inc.'s GV-Eye Android application version 3.6.0 where an API key is hardcoded and can be extracted from the application package. This exposure allows unauthorized users to retrieve sensitive credentials due to the ease of reverse engineering Android apps.

CVSS v3.1

Score 7.5high

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Affected software

GeoVision Inc.

GV-Eye

Affected versions
=3.6.0

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 10/02/2026, 01:16:07 UTC

Technical Analysis

The vulnerability involves the use of hardcoded API credentials embedded directly within the GV-Eye Android application package (version 3.6.0). Because Android applications can be reverse engineered, attackers can extract these credentials, potentially leading to unauthorized access or misuse of the API key. The CVSS v3.1 base score is 7.5, reflecting a high severity with network attack vector, low attack complexity, no privileges required, no user interaction, and high confidentiality impact but no integrity or availability impact.

Potential Impact

An attacker who extracts the hardcoded API key can misuse it to access backend services or APIs intended to be protected, potentially leading to unauthorized data access or service abuse. However, there is no indication of integrity or availability impact. No known exploits are reported in the wild at this time.

Mitigation Recommendations

No official patch or remediation is currently available for this vulnerability. Users should monitor vendor advisories for updates. As a best practice, avoid embedding sensitive credentials in client applications. Consider implementing server-side authentication mechanisms or dynamic credential provisioning to mitigate risks.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
GV
Date Reserved
2026-09-30T02:10:01.788Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 6abf028fa43b0b3b89382320

Added to database: 10/02/2026, 01:02:07 UTC

Last enriched: 10/02/2026, 01:16:07 UTC

Last updated: 10/02/2026, 01:38:20 UTC

Views: 5

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses