CVE-2026-122152: The ICRTouch white-label TouchTakeaway Cordova applications do not implement certificate or
Source GCVE Database
Not known to be exploited.
Data as of 17 Nov 2026, 20:04 UTC
Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD
Thin evidence
One scorer or noneExploitation evidence
Disclosed: evidence found.
CVE published 17 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 16 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| ICRTouchTouchTakeaway | Affected
| Fixed in– |
AI-suggested
Users and administrators should monitor vendor advisories for updates. Implementing certificate or public-key pinning in the application would mitigate this risk by ensuring only trusted certificates are accepted, but this requires an update from the vendor.
Description
The ICRTouch white-label TouchTakeaway Cordova applications do not implement certificate or public-key pinning for backend HTTPS connections, relying solely on the device's system trust store for server certificate validation. This lack of pinning means that if an attacker can cause the device to trust a malicious certificate authority or use a compromised trusted certificate, they may intercept and modify the application's network traffic.