CVE-2025-61691VulnerabilityPublished 2 Oct 2025

CVE-2025-61691: KEYENCE VT STUDIO · Out-of-bounds Read

Affects KEYENCE VT STUDIOSource CVE Database V5

Not known to be exploited · CVSS 7.8 High.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

7.8High

How severe the flaw is on the 0–10 CVSS scale.

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:N/UI:R/S:U/C:H/I:H/A:H

Attack Vector: Local
Attack Complexity: Low
Privileges Required: None
User Interaction: Required
Scope: Unchanged
Confidentiality: High
Integrity: High
Availability: High

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Local: The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either: the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or remotely (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., tricking a legitimate user into opening a malicious document).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 2 Oct 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.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
KEYENCE CORPORATION VT STUDIO	Affected <=8.53	Fixed in–

AI-suggested

European organizations should take immediate steps to mitigate the risk posed by CVE-2025-61691. First, they should restrict access to VT STUDIO installations to trusted personnel only and enforce strict access controls to minimize the risk of local exploitation. Implementing application whitelisting and endpoint protection solutions can help detect and block attempts to execute malicious code. Organizations should educate users about the risks of opening files from untrusted sources and enforce policies to avoid processing files from unknown origins. Network segmentation between IT and OT environments can limit the spread of an attack if exploitation occurs. Since no patches are currently available, organizations should monitor KEYENCE CORPORATION's advisories closely and apply updates as soon as they are released. Additionally, conducting regular security audits and vulnerability assessments on systems running VT STUDIO can help identify potential exposure. Employing intrusion detection systems (IDS) and monitoring logs for unusual activity related to VT STUDIO usage can provide early warning signs of exploitation attempts.

Description

VT STUDIO versions 8.53 and prior contain an out-of-bounds read vulnerability. If the product uses a specially crafted file, arbitrary code may be executed on the affected product.

Impact

For European organizations, especially those involved in manufacturing, industrial automation, and critical infrastructure sectors, this vulnerability poses a significant threat. VT STUDIO is used to design and simulate industrial control systems, and compromise of this software could lead to unauthorized code execution within operational technology (OT) environments. This could result in manipulation of industrial processes, data breaches involving sensitive operational data, or disruption of production lines. Given the high confidentiality, integrity, and availability impact, exploitation could cause financial losses, safety hazards, and reputational damage. Additionally, the requirement for user interaction means that social engineering or phishing campaigns could be used to trick operators into opening malicious files. The local attack vector suggests that attackers would need some level of access to the target system, which could be achieved through compromised credentials or insider threats. The absence of known exploits in the wild currently reduces immediate risk but does not eliminate it, as threat actors may develop exploits rapidly after vulnerability disclosure.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 2 Oct 2025, 18:06 UTC

Technical details

References

Community reviews

Related threats