CVE
ICRTouch PocketTouch cleartext credential leak in POS socket link
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
- Exploited
- No known exploitation
- Fix
- See vendor advisory
- Who is exposed
- Not reported
Do first: Workaround: No fix is listed yet. Limiting who can observe the local network traffic between PocketTouch and the POS terminal is the main step the facts support; no specific workaround is named in the sources.
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- 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? →
- 33/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
- Exploitation: none
- Automatable: yes
- Technical impact: partial
Summary
ICRTouch PocketTouch transmits the POS socket password in plaintext XML over an unencrypted TCP connection, so anyone who can observe traffic between a PocketTouch device and a TouchPoint POS terminal can recover the password from captured packets.
Written by a model from the sources below. Verify against them.
Original description
ICRTouch PocketTouch version 1.700 build 2025.3726 transmits the POS socket password in plaintext XML over an unencrypted TCP connection. The protocol does not provide transport-layer encryption to protect credentials from interception.
An attacker able to observe network traffic between a PocketTouch device and a TouchPoint POS terminal can recover the socket password from captured packets.
Who should check
Teams running ICRTouch PocketTouch v1.700 (build 2025.3726) on Android tablets that connect to TouchPoint POS terminals over a local network.
“Affected version: PocketTouch v1.700 (build 2025.3726).”
cve.now Index
- Exploitation0/40No signal
- Exposure20/25No login or user action needed, CISA rates it automatable · Unknown: Advisories don't say whether default setups are affected
- Reach?/20Unknown. No tracked technology or package matched
- Severity7.5/10CVSS 7.5
- No patch5/5No fixed version listed; see vendor advisory
What would change the score
- Would score about 78 if added to CISA KEV
- Would score about 73 if CISA's SSVC rates exploitation active
- Would score about 38 if advisories confirm default setups are exposed
What to do
Workaround: No fix is listed yet. Limiting who can observe the local network traffic between PocketTouch and the POS terminal is the main step the facts support; no specific workaround is named in the sources.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-122145 (CVE-2026-122145), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-122145 (entry last updated 2026-11-17):
Affected:
- ICRTouch PocketTouch: version 1.700
Fixed versions: none listed yet.
Conditions (all must be true for the bug to be hit):
- Affected product is ICRTouch PocketTouch v1.700 (build 2025.3726). (source: https://codevispera.com/research/vu-223386/)
- PocketTouch connects to the venue's POS terminal over the local network, so the attacker must be able to observe that traffic. (source: https://codevispera.com/research/vu-223386/)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-122145 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-122145 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- http://icrtouch.com
- https://codevispera.com/research/vu-223386/
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-122145
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-122145"}.Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: partial
- Record last updated
Affected versions
- ICRTouch PocketTouch
From 1.700 · through 1.700
Evidence 4
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Other links · 1
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-122145
Is CVE-2026-122145 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?
PocketTouch sends the POS socket password in plaintext over the local network, without transport encryption. Someone who can observe that traffic can recover the password from captured packets.Source: codevispera.com
Which versions are affected by CVE-2026-122145?
PocketTouch: from 1.700 through 1.700.Source: cve.now feed data
Am I affected, and how do I check?
Only ICRTouch PocketTouch v1.700 (build 2025.3726) is listed as affected. The product connects to the venue's POS terminal over the local network, so the exposure depends on whether that traffic can be observed.Source: codevispera.com
How do I fix CVE-2026-122145?
No fixed version or vendor patch is named in the checked facts, so no upgrade target is available to recommend.Source: codevispera.com
What if there's no patch?
No fix is listed yet. Limiting who can observe the local network traffic between PocketTouch and the POS terminal is the main step the facts support; no specific workaround is named in the sources.Source: codevispera.com