CVE-2026-111495: API keys, credentials, and configuration parameters embedded in the MatchPoint APK, which can be
Source GCVE Database
Not known to be exploited · CVSS 5.1 Medium · patch available : update Matchpoint when convenient.
Data as of 6 Nov 2026, 01:20 UTC
Thin evidence
One scorer or none| CNA (INCIBE) | CVSS 4.0 | 5.1 |
|---|
- Patch
- Available
CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 5 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 5 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| TPC SoftwareMatchpoint | Affected
| Fixed in– |
AI-suggested
Since the vendor classifies some keys as non-sensitive project identifiers, no immediate action may be required. Organizations should review the permissions and restrictions of exposed keys and consider rotating or restricting keys if feasible.
Description
The MatchPoint APK contains embedded API keys, credentials, and configuration parameters that can be extracted via reverse engineering. The vendor clarifies that some of these elements, such as Google Maps and Firebase keys, are project identifiers rather than authentication secrets. The security impact varies depending on the specific capabilities and restrictions of the exposed elements. No known exploits are reported in the wild, and no patches or fixes have been indicated.