CVE-2026-122153: The TouchOffice API clerkList endpoint appears to return sensitive clerk authentication data
Source GCVE Database
Not known to be exploited · CVSS 7.5 High.
Data as of 17 Nov 2026, 20:04 UTC
Thin evidence
One scorer or none| CISA-ADP | CVSS 3.1 | 7.5 |
|---|
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:NExploitation 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 |
|---|---|---|
| ICRTouchTouchOffice | Affected
| Fixed in– |
AI-suggested
Until a fix is available, restrict access to the clerkList endpoint to authorized users only to prevent exposure of sensitive authentication data.
Description
The TouchOffice API's clerkList endpoint returns sensitive authentication data such as clerk PINs and iButton serial numbers. This exposure allows unauthorized callers to access reusable authentication credentials beyond what is necessary for listing clerks.