CVE
ICRTouch Commander API key exposure in administrative interface
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: The checked facts give no workaround. The exposure comes from the API key being sent in the query string of GET requests, so the key can be written to any logs and history those requests pass through.
- 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 Commander's administrative interface performs security-sensitive operations through HTTP GET requests and places an API key in the request query string. Because such requests are often recorded in browser history, proxy and server logs, and referrer headers, anyone able to read those records could obtain the key.
Written by a model from the sources below. Verify against them.
Original description
ICRTouch Commander administrative interface performs security-sensitive operations through HTTP GET requests and includes an API key in the request query string. GET requests are commonly retained in browser history, proxy logs, server logs, analytics systems, referrer headers, and other intermediary records.
Who should check
Teams running production ICRTouch Commander, the cloud management console, and anyone whose API keys are used with it.
“ByTable, Commander, and TouchTakeaway: production versions at the time of research.”
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: The checked facts give no workaround. The exposure comes from the API key being sent in the query string of GET requests, so the key can be written to any logs and history those requests pass through.
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-122143 (CVE-2026-122143), 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-122143 (entry last updated 2026-11-17):
Affected:
- ICRTouch Commander: from 1, through 2
Fixed versions: none listed yet.
Conditions (all must be true for the bug to be hit):
- Affected product is ICRTouch Commander, production versions at the time of research. (source: https://codevispera.com/research/vu-223386/)
- Commander sends security-sensitive operations as HTTP GET requests with the API key in the query string. (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-122143 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-122143 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-122143
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-122143"}.Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: partial
- Record last updated
Affected versions
- ICRTouch Commander
From 1 · through 2
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-122143
Is CVE-2026-122143 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?
ICRTouch Commander sends security-sensitive operations as HTTP GET requests with the API key in the query string. GET parameters can persist in browser history, proxy logs, server access logs and referrer headers, where the key can be read from those records.Source: codevispera.com
Which versions are affected by CVE-2026-122143?
Commander: from 1 through 2.Source: cve.now feed data
Am I affected, and how do I check?
The listed affected range is ICRTouch Commander versions 1 through 2, covering production versions at the time of research. To check an installed copy, look up its Commander version in the product's own version information.Source: codevispera.com
How do I fix CVE-2026-122143?
The checked facts name no fixed version and no vendor patch IDs, so no upgrade target can be given from them. Check the vendor's advisory for a fixed release.Source: codevispera.com
What if there's no patch?
The checked facts give no workaround. The exposure comes from the API key being sent in the query string of GET requests, so the key can be written to any logs and history those requests pass through.Source: codevispera.com