Skip to main content

An API key is hardcoded and retrievable from the application package. (CVE-2026-103097)

0
High
Published: 10/02/2026 (10/02/2026, 03:31:10 UTC)
Source: GCVE Database

Description

This vulnerability involves an API key that is hardcoded and retrievable from the application package. Because Android applications can be reverse engineered, embedding sensitive API credentials directly in the client application risks unauthorized extraction and misuse of the key. The vulnerability has a high severity score of 7.5 (CVSS 3.1) with network attack vector and no privileges required for exploitation.

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

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 10/02/2026, 18:24:02 UTC

Technical Analysis

CVE-2026-103097 describes a vulnerability where an API key is embedded directly within an Android application package. Since Android apps can be reverse engineered, attackers can extract this hardcoded key without needing privileges or user interaction. The vulnerability has a CVSS 3.1 base score of 7.5, indicating high severity due to the potential confidentiality impact of unauthorized access to the API key. No information about patches or fixes is provided, and the affected versions are not specified.

Potential Impact

The impact is primarily the unauthorized disclosure of a sensitive API key, which can lead to misuse of the associated API or service. The confidentiality of the key is compromised, but there is no direct indication of integrity or availability impact. Exploitation does not require privileges or user interaction, making it easier for attackers to extract the key from the application package.

Mitigation Recommendations

No patch or official fix information is provided. Since this vulnerability arises from insecure coding practices (hardcoding sensitive credentials), the recommended mitigation is to avoid embedding API keys directly in client-side applications. Instead, use secure methods such as retrieving keys from a secure backend or employing token-based authentication mechanisms. Monitor vendor advisories for any updates or official remediation guidance.

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

Technical Details

Gcve Source
db.gcve.eu
Osv Id
GHSA-mwfx-8rgq-rc8f
Osv Schema Version
1.4.0
Aliases
["CVE-2026-103097"]
Database Specific Severity
HIGH
Cvss Version
3.1
State
PUBLISHED

Threat ID: 6abfeec2a43b0b3b89e5788c

Added to database: 10/02/2026, 17:49:54 UTC

Last enriched: 10/02/2026, 18:24:02 UTC

Last updated: 10/02/2026, 18:45:56 UTC

Views: 2

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