CVE-2026-103096
Received Received - Intake

Hardcoded API Key in Android Application

Publication date: 2026-10-02

Last updated on: 2026-10-02

Assigner: GV

Description
API key is hardcoded and retrievable from the application package. Since Android applications can be reverse engineered, embedding sensitive API credentials directly in the client application may allow unauthorized users to extract and misuse the key.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-10-02
Last Modified
2026-10-02
Generated
2026-10-02
AI Q&A
2026-10-02
EPSS Evaluated
N/A
NVD
CVE-2026-103096
EUVD
EUVD-2026-91146

Affected Vendors & Products

Currently, no data is known.

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-798 The product contains hard-coded credentials, such as a password or cryptographic key.
CWE-540 Source code on a web server or repository often contains sensitive information and should generally not be accessible to users.
CWE-312 The product stores sensitive information in cleartext within a resource that might be accessible to another control sphere.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability involves an API key that is hardcoded into an Android application's package. Since Android apps can be reverse engineered, attackers can extract and misuse this key, potentially gaining unauthorized access to the API.

Detection Guidance

This vulnerability involves a hardcoded API key in an Android application, which can be extracted through reverse engineering. To detect it, inspect the application package for embedded credentials using tools like apktool to decompile the APK and search for API keys in the code or configuration files.

Impact Analysis

If you use an affected application, attackers could extract the hardcoded API key and misuse it to make unauthorized requests, leading to data breaches, service disruptions, or financial losses. The CVSS score of 7.5 indicates a high severity risk.

Compliance Impact

This vulnerability could lead to unauthorized data access or exposure, violating GDPR's data protection requirements and HIPAA's safeguards for protected health information. Non-compliance may result in legal penalties and reputational damage.

Mitigation Strategies

Remove or obfuscate hardcoded API keys in the application package to prevent extraction through reverse engineering. Review and update application code to use secure credential storage methods.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-103096. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart