CVE-2026-0500: SAP Wily Introscope Enterprise Manager (WorkStation) · Improper Control of Generation of Code
Affects SAP Wily Introscope Enterprise Manager (WorkStation)Source CVE Database V5
Not known to be exploited · CVSS 9.6 Critical.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 35% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 13 Jan 2026
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 |
|---|---|---|
| SAP_SESAP Wily Introscope Enterprise Manager (WorkStation) | Affected
| Fixed in– |
AI-suggested
To mitigate CVE-2026-0500, European organizations should take immediate and specific actions beyond generic best practices: 1) Identify and inventory all instances of SAP Wily Introscope Enterprise Manager version 10.8 in their environment. 2) Restrict public access to URLs serving JNLP files by implementing strict access controls, network segmentation, and firewall rules to limit exposure. 3) Educate users about the risks of clicking unknown or suspicious links, especially those involving JNLP files or Java applications. 4) Monitor network traffic and logs for unusual access patterns to JNLP URLs or unexpected command execution attempts. 5) Engage with SAP support or trusted security vendors to obtain patches or workarounds as soon as they become available, as no official patches are currently listed. 6) Consider disabling or restricting the use of JNLP file handling in the affected product if feasible, or deploy application whitelisting to prevent unauthorized code execution. 7) Implement endpoint detection and response (EDR) solutions to detect and block suspicious OS command executions triggered by JNLP files. 8) Conduct phishing simulations and reinforce security awareness training to reduce the likelihood of successful social engineering attacks. These targeted measures will reduce the attack surface and improve detection and response capabilities against exploitation attempts.
Description
Due to the usage of vulnerable third party component in SAP Wily Introscope Enterprise Manager (WorkStation), an unauthenticated attacker could create a malicious JNLP (Java Network Launch Protocol) file accessible by a public facing URL. When a victim clicks on the URL the accessed Wily Introscope Server could execute OS commands on the victim's machine. This could completely compromising confidentiality, integrity and availability of the system.