CVE-2025-65570: n/a
Source CVE Database V5
Not known to be exploited · CVSS 9.8 Critical.
Data as of 26 Oct 2026, 06:26 UTC
- EPSS
- 0.5% chance of exploitation in 30 days – higher than 44% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 29 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-26.
What to do
AI-suggested
Given the absence of an official patch at this time, European organizations should implement several specific mitigations: 1) Conduct an inventory to identify all instances of jsish 2.0 usage within software and embedded systems. 2) Where possible, disable or restrict the use of scripting features that rely on the vulnerable OP_NEXT and OP_INSTANCEOF bytecode operations, particularly for-in loops involving instanceof expressions with array elements. 3) Employ runtime application self-protection (RASP) or memory protection mechanisms such as Control Flow Integrity (CFI) and Address Space Layout Randomization (ASLR) to reduce exploitation success. 4) Monitor application logs and system behavior for crashes or anomalous activity indicative of exploitation attempts. 5) Engage with software vendors and open-source communities to track patch releases and apply updates promptly once available. 6) For critical systems, consider isolating or sandboxing components using jsish to limit the blast radius of a potential compromise. 7) Implement network-level protections such as firewalls and intrusion detection systems tuned to detect exploitation patterns targeting jsish vulnerabilities. These targeted steps go beyond generic advice by focusing on the specific nature of the vulnerability and the operational context of jsish.
Description
A type confusion in jsish 2.0 allows incorrect control flow during execution of the OP_NEXT opcode. When an “instanceof” expression uses an array element access as the left-hand operand inside a for-in loop, the instructions implementation leaves an additional array reference on the stack rather than consuming it during OP_INSTANCEOF. As a result, OP_NEXT interprets the array as an iterator object and reads the iterCmd function pointer from an invalid structure, potentially causing a crash or enabling code execution depending on heap layout.