Incorrect validation of TLS certificates in the MatchPoint Android app
- Exploited
- No known exploitation
- Fix
- No fix listed
- Who is exposed
- Not reported
Do first: Workaround: The facts list no fix and no workaround. The sources do not describe a mitigation, so the available guidance is to watch the vendor's advisory for a fix.
- Last modified
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 31/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Unclear
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
The MatchPoint Android app does not properly validate TLS certificates and allows unencrypted HTTP traffic, so an attacker who can intercept its network traffic can remotely, without logging in, read and modify communications, including credentials and personal data.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Read the original description
Incorrect validation of TLS certificates in the MatchPoint Android app due to a TrustManager that accepts any certificate and a permissive hostname validator. Additionally, the app allows unencrypted HTTP traffic. An attacker capable of intercepting the victim's traffic could read and modify communications, including credentials and personal data.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure17/25No login or user action needed, reachable over the network without a login · Unknown: Advisories don't say whether default setups are affected
- Reach?/20Unknown. No tracked technology or package matched
- Severity9.1/10CVSS 9.1
- No patch5/5No patch listed yet
What would change the score
- Would score about 76 if added to CISA KEV
- Would score about 71 if CISA's SSVC rates exploitation active
- Would score about 36 if advisories confirm default setups are exposed
What to do
Workaround: The facts list no fix and no workaround. The sources do not describe a mitigation, so the available guidance is to watch the vendor's advisory for a fix.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- TPC Software Matchpoint
Version range not reported
Evidence 1
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-111494
Is CVE-2026-111494 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
The MatchPoint Android app does not properly validate TLS certificates. An attacker who can intercept the victim's traffic could read and modify communications, including credentials and personal data.Source: incibe.es
Am I affected, and how do I check?
The facts name only the MatchPoint Android app from TPC Software and list no affected version ranges. The sources do not say which app versions contain the flaw.Source: incibe.es
How do I fix CVE-2026-111494?
The facts give no fixed version, so no upgrade target can be named. Check the vendor's advisory for an updated release.Source: incibe.es
What if there's no patch?
The facts list no fix and no workaround. The sources do not describe a mitigation, so the available guidance is to watch the vendor's advisory for a fix.Source: incibe.es