CVE-2025-1095: IBM Personal Communications · Unprotected Alternate Channel
Affects IBM Personal CommunicationsSource CVE Database V5
Mentioned vulnerabilities
Not known to be exploited · CVSS 8.8 High.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 3% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 8 Apr 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 2026-10-25.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| IBM Personal Communications | Affected
| Fixed in– |
AI-suggested
Until an official patch is released by IBM, organizations should implement several specific mitigations: 1) Restrict local user accounts to the minimum necessary privileges and disable or remove unnecessary interactive logins on systems running IBM Personal Communications. 2) Employ application whitelisting and endpoint detection and response (EDR) solutions to monitor and block suspicious command executions originating from IBM Personal Communications processes or related services. 3) Use Windows security features such as AppLocker or Software Restriction Policies to limit execution of unauthorized binaries or scripts. 4) Audit and monitor Windows event logs for unusual privilege escalation attempts or service interactions related to IBM Personal Communications. 5) Isolate systems running the affected software from less trusted users and networks to reduce exposure. 6) Prepare to deploy patches promptly once IBM releases them, and test updates in controlled environments before widespread rollout. 7) Educate local users about the risks of executing untrusted code or commands on affected systems. These targeted controls go beyond generic advice by focusing on minimizing local attack surface and enhancing detection capabilities specific to this vulnerability.
Description
IBM Personal Communications v14 and v15 include a Windows service that is vulnerable to local privilege escalation (LPE). The vulnerability allows any interactively logged in users on the target computer to run commands with full privileges in the context of NT AUTHORITY\SYSTEM. This allows for a low privileged attacker to escalate their privileges. This vulnerability is due to an incomplete fix for CVE-2024-25029.