External risk intelligence

PocketTouch and TouchPoint SAVECONFIG Command Allows Remote Configuration File Overwrite.

CVE advisorySeverity: CRITICAL (CVSS 9.1)

CVE-2026-122149

The vulnerability involves a POS protocol and socket service. While network-reachable, Point-of-Sale systems are typically deployed within isolated internal store networks and are not intended to be directly exposed to the public internet. Public internet exposure for such services is uncommon and generally considered a misconfiguration.

Missing Authentication

Halo Surface Signal: 2 out of 5 — less likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

This advisory details a critical vulnerability within the PocketTouch and TouchPoint Point-of-Sale (POS) protocol, specifically involving a `SAVECONFIG` command that could allow remote modification or replacement of terminal configuration files. An attacker with network access could potentially exploit this to alter critical settings. The main concern is confirming if your POS systems are exposed to this type of network access.

  • Protocol command allows configuration file overwrite.
  • Critical for confirming POS system exposure.
  • Assess if your POS systems are directly network-accessible.

Attack Path

How an attacker could exploit the issue

An attacker who can reach the Point-of-Sale (POS) system over a network could send a special command to overwrite critical configuration files. This could lead to unauthorized modifications or replacements of terminal data.

  • Attacker needs network access.
  • Malicious `SAVECONFIG` command.
  • Uncontrolled configuration data modification.

Live Threat

Current exploitation, exposure, and threat context

A network-accessible attacker could potentially overwrite till configuration files for PocketTouch and TouchPoint Point-of-Sale (POS) systems by sending a specially crafted `SAVECONFIG` command. This could alter how the terminals operate.

  • Terminal configuration data.
  • Sending crafted `SAVECONFIG` command.
  • Altered till operations.

Operational Fix

Recommended remediation, mitigation, and detection steps

This vulnerability in the PocketTouch and TouchPoint POS protocol may allow an attacker with network access to overwrite till configuration files remotely. System owners and security teams should first confirm the presence and network reachability of the affected POS systems, identify the business criticality, and then determine the accountable owner for remediation planning.

  • Identify POS systems and critical assets.
  • Verify network exposure and business impact.
  • Plan vendor-assisted configuration review.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is the PocketTouch and TouchPoint software?

PocketTouch and TouchPoint are Point-of-Sale (POS) systems used by businesses to process transactions and manage terminal operations. These systems rely on a specific network protocol to communicate between devices and handle essential configuration settings that dictate how a checkout till functions.

What does CVE-2026-122149 mean in plain English?

This vulnerability is classified as Missing Authentication for Critical Function (CWE-306). It means the POS protocol lacks a necessary security check when processing the SAVECONFIG command. Consequently, the system accepts configuration changes from the network without verifying if the sender is authorized, allowing unauthorized modification of critical terminal data.

How does an attacker trigger this vulnerability?

An attacker triggers the bug by sending a specially crafted SAVECONFIG command to the POS socket service over the network. This does not require any local interaction or prior user authentication. Note that simply communicating with the POS device through authorized, legitimate administrative tools does not trigger this unintended configuration overwrite.

Do I need to worry if my systems are on an internal network?

According to Halo Surface Signal, this vulnerability is most relevant to systems with public internet exposure, which is uncommon for POS hardware. While internal access is theoretically possible, these devices are typically meant to reside within isolated store networks, limiting the pool of potential attackers who could reach the vulnerable socket service.

When should I take action on my POS systems?

You should prioritize identifying where these POS terminals exist in your network and confirming whether they are reachable from outside your local environment. Once you have mapped these assets and their business criticality, engage your vendor to plan for a secure configuration review and apply any forthcoming updates to secure the protocol.

References