Skip to main content
Menu
CVEs

CVE

ICRTouch PocketTouch auth bypass via hard-coded passwords in shutdown functions

Only affects ICRTouch PocketTouch version 1.700 (build 2025.3726), which ships with hard-coded default credentials. CVSS rates it critical at 9.8. No fixed version is listed.

CVE-2026-122147EUVD-2026-127063

Written by a model from the sources below. Verify against them.

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

9.8CriticalCISA-ADP
Exploited
No known exploitation
Fix
See vendor advisory
Who is exposed
Not reported

Do first: Workaround: The checked facts list no workaround. Until a fix is published, the advisory's mitigation guidance is not available in these sources.

Published
Last modified
Reference
Last checked
35/100 · provisional
Unclear
None on Exploit-DB, Metasploit or GitHub
On X
View the cve.now post
  • Exploitation: none
  • Automatable: yes
  • Technical impact: total

Summary

ICRTouch PocketTouch contains hard-coded default passwords for its socket, configuration, and shutdown functions, so anyone who knows these defaults could potentially use those functions. An additional email-related password field is also initialized without a value.

Original description

ICRTouch PocketTouch version 1.700 build 2025.3726 defines hard-coded default values for multiple credential fields, including a socket password and configuration and shutdown passwords. An additional email-related password field is initialized without a value.

Who should check

Anyone running ICRTouch PocketTouch v1.700 (build 2025.3726), the Android mobile POS app used by floor staff.

“Affected version: PocketTouch v1.700 (build 2025.3726)”

codevispera.com

cve.now Index

35Pcve.now Index 35 of 100 · methodology v3 · provisional
  • 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
  • Severity10/10CVSS 9.8, total technical impact per CISA
  • No patch5/5No fixed version listed; see vendor advisory

What would change the score

  • Would score about 80 if added to CISA KEV
  • Would score about 75 if CISA's SSVC rates exploitation active
  • Would score about 40 if advisories confirm default setups are exposed

What to do

  • Workaround: The checked facts list no workaround. Until a fix is published, the advisory's mitigation guidance is not available in these 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-122147 (CVE-2026-122147), 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-122147 (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):
- ICRTouch PocketTouch version 1.700 build 2025.3726 (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-122147 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-122147 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-122147
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-122147"}.

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: none · Automatable: yes · Technical impact: total

  4. Record last updated
  5. Posted on X by cve.now

Affected versions

  • ICRTouch PocketTouch

    From 1.700 · through 1.700

Evidence 4

Vendor advisory · 1

Establishes: Affected and fixed versions.

  1. Link

CVE record · 2

Establishes: The identifier and description.

  1. Record
  2. Record

Other links · 1

  1. Link

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-122147

Is CVE-2026-122147 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 ships with hard-coded default values for several credential fields, including a socket password and configuration and shutdown passwords. Because these defaults are built into the product, anyone who knows them could use them to access the affected functions.Source: codevispera.com

Which versions are affected by CVE-2026-122147?

PocketTouch: from 1.700 through 1.700.Source: cve.now feed data

Am I affected, and how do I check?

The advisory names only PocketTouch v1.700 (build 2025.3726). To check a installation, look at the PocketTouch version and build shown by the product.Source: codevispera.com

How do I fix CVE-2026-122147?

The checked facts list no fixed version and no vendor patch IDs, so no upgrade target is available from these sources. Check the vendor's advisory or support channel for an update.Source: codevispera.com

What if there's no patch?

The checked facts list no workaround. Until a fix is published, the advisory's mitigation guidance is not available in these sources.Source: codevispera.com

More CVEs