CVE-2025-12556: IDIS ICM Viewer · Argument Injection
Affects IDIS ICM ViewerSource CVE Database V5
Not known to be exploited · CVSS 8.7 High.
Data as of 26 Oct 2026, 15:59 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 40% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 6 Nov 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: 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 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| IDIS ICM Viewer | Affected
| Fixed in– |
AI-suggested
- Monitor IDIS communications for official patches addressing CVE-2025-12556 and apply them immediately upon release.
- Restrict network access to the IDIS ICM Viewer application by implementing firewall rules that limit connections to trusted IP addresses and networks only.
- Employ network segmentation to isolate surveillance systems from general enterprise networks, reducing lateral movement opportunities.
- Implement strict input validation and command execution controls where possible, including application whitelisting and behavior monitoring to detect anomalous command invocations.
- Conduct regular security audits and vulnerability scans focusing on the affected software version to identify and remediate exposures.
- Enhance logging and monitoring of the ICM Viewer environment to detect suspicious activities indicative of exploitation attempts.
- Educate IT and security personnel about the vulnerability and the importance of rapid patch management and incident response readiness.
- Consider temporary disabling or limiting use of vulnerable features if feasible until patches are applied. These measures go beyond generic advice by focusing on network-level controls, monitoring, and operational readiness specific to the affected product and vulnerability type.
Description
An argument injection vulnerability exists in the affected product that could allow an attacker to execute arbitrary code within the context of the host machine.