CVE-2025-43875: Johnson Controls iSTAR Ultra, iSTAR Ultra SE · OS Command Injection
Affects Johnson Controls iSTAR Ultra, iSTAR Ultra SESource CVE Database V5
Not known to be exploited · CVSS 8.7 High.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 22% 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 24 Dec 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 |
|---|---|---|
| Johnson Controls iSTAR Ultra, iSTAR Ultra SE | Affected
| Fixed in– |
AI-suggested
1. Immediately verify if your Johnson Controls iSTAR Ultra or iSTAR Ultra SE devices are affected and prioritize patching once vendor updates become available. 2. Until patches are released, restrict access to the web management interface to trusted administrative networks only, using network segmentation and firewall rules. 3. Enforce strong authentication mechanisms and limit user privileges to the minimum necessary to reduce the risk of privilege escalation. 4. Monitor device logs and network traffic for unusual command execution patterns or unauthorized access attempts. 5. Implement multi-factor authentication (MFA) for device management interfaces where possible. 6. Conduct regular security audits and penetration testing focused on physical security systems. 7. Engage with Johnson Controls support channels for updates and guidance. 8. Consider deploying intrusion detection/prevention systems (IDS/IPS) tuned to detect command injection attempts targeting these devices. 9. Maintain an incident response plan specific to physical security system compromises.
Description
Under certain circumstances a successful exploitation could result in access to the device.