A vulnerability categorized as problematic has been discovered in Japan Computer Emergency Response Team Coordination Center Emocheck . This affects an unknown part. Such manipulation leads to uncontrolled search path. This vulnerability only affects products that are no longer supported by the maintainer. This vulnerability is listed as CVE-2026-28704 . The attack must be carried out locally. There is no available exploit.
Full text archived locally
✦ AI Summary· Claude Sonnet
VDB-356799 · CVE-2026-28704 · GCVE-0-2026-28704
EMOCHECK UNCONTROLLED SEARCH PATH
HISTORYDIFFRELATEJSONXMLCTI
CVSS Meta Temp Score Current Exploit Price (≈) CTI Interest Score
7.4 $0-$5k 1.31+
Summaryinfo
A vulnerability identified as problematic has been detected in Japan Computer Emergency Response Team Coordination Center Emocheck. This vulnerability affects unknown code. Performing a manipulation results in uncontrolled search path. This vulnerability only affects products that are no longer supported by the maintainer. This vulnerability is cataloged as CVE-2026-28704. The attack must be initiated from a local position. There is no exploit available.
Detailsinfo
A vulnerability, which was classified as critical, was found in Japan Computer Emergency Response Team Coordination Center Emocheck (affected version not known). This affects some unknown functionality. The manipulation with an unknown input leads to a uncontrolled search path vulnerability. CWE is classifying the issue as CWE-427. The product uses a fixed or controlled search path to find resources, but one or more locations in that path can be under the control of unintended actors. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
Emocheck insecurely loads Dynamic Link Libraries (DLLs). If a crafted DLL file is placed to the same directory, an arbitrary code may be executed with the privilege of the user invoking EmoCheck.
It is possible to read the advisory at jpcert.or.jp. This vulnerability is uniquely identified as CVE-2026-28704 since 04/03/2026. The exploitability is told to be difficult. Attacking locally is a requirement. The technical details are unknown and an exploit is not publicly available. The pricing for an exploit might be around USD $0-$5k at the moment (estimation calculated on 04/10/2026). The attack technique deployed by this issue is T1574 according to MITRE ATT&CK.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Productinfo
Vendor
Japan Computer Emergency Response Team Coordination Center
Name
Emocheck
Support
end of life
CPE 2.3info
🔒
CPE 2.2info
🔒
CVSSv4info
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒
CVSSv3info
VulDB Meta Base Score: 7.4
VulDB Meta Temp Score: 7.4
VulDB Base Score: 7.0
VulDB Temp Score: 7.0
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 7.8
CNA Vector (jpcert): 🔒
CVSSv2info
Vector Complexity Authentication Confidentiality Integrity Availability
Unlock Unlock Unlock Unlock Unlock Unlock
Unlock Unlock Unlock Unlock Unlock Unlock
Unlock Unlock Unlock Unlock Unlock Unlock
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploitinginfo
Class: Uncontrolled search path
CWE: CWE-427 / CWE-426
CAPEC: 🔒
ATT&CK: 🔒
Physical: Partially
Local: Yes
Remote: Partially
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
0-Day Unlock Unlock Unlock Unlock
Today Unlock Unlock Unlock Unlock
Threat Intelligenceinfo
Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍
Countermeasuresinfo
Recommended: no mitigation known
Status: 🔍
0-Day Time: 🔒
Timelineinfo
04/03/2026 CVE reserved
04/10/2026 +7 days Advisory disclosed
04/10/2026 +0 days VulDB entry created
04/10/2026 +0 days VulDB entry last update
Sourcesinfo
Advisory: jpcert.or.jp
Status: Not defined
CVE: CVE-2026-28704 (🔒)
GCVE (CVE): GCVE-0-2026-28704
GCVE (VulDB): GCVE-100-356799
Entryinfo
Created: 04/10/2026 08:58
Changes: 04/10/2026 08:58 (73)
Complete: 🔍
Cache ID: 99:B4D:101
Discussion
No comments yet. Languages: en.
Please log in to comment.
◂ PreviousOverviewNext ▸