CVE-2025-22463: Ivanti Workspace Control · Use of Hard-coded Cryptographic Key
Affects Ivanti Workspace ControlSource CVE Database V5
Not known to be exploited · CVSS 7.3 High : upgrade to 10.19.10.0 soon.
Data as of 26 Oct 2026, 07:57 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 29% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 10.19.10.0
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:LExploitation evidence
Disclosed: evidence found.
CVE published 10 Jun 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-26.
What to do
Upgrade Ivanti Workspace Control to 10.19.10.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Ivanti Workspace Control | Affected
| Fixed in
|
AI-suggested
To mitigate CVE-2025-22463, organizations should take several specific actions beyond generic advice: 1) Restrict local access to systems running Ivanti Workspace Control to trusted administrators only, minimizing the number of users with authenticated local access. 2) Implement strict endpoint security controls, including application whitelisting and behavior monitoring, to detect and prevent unauthorized local access or suspicious activities. 3) Monitor logs and audit trails for unusual access patterns or attempts to access encrypted environment password stores. 4) Prepare for prompt deployment of official patches or updates from Ivanti once available; in the meantime, consider temporary workarounds such as disabling features that store environment passwords if feasible. 5) Educate users and administrators about the risks of local credential exposure and enforce strong authentication and privilege separation policies. 6) Conduct regular security assessments and penetration testing focusing on local privilege escalation vectors. 7) If possible, isolate critical systems using Ivanti Workspace Control in segmented network zones to limit lateral movement in case of compromise.
Description
A hardcoded key in Ivanti Workspace Control before version 10.19.10.0 allows a local authenticated attacker to decrypt the stored environment password.