Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessCraft tar dictionary file with overflow size field
-
DeliveryDeliver file to CorvusSKK user
-
ExploitUser opens file in CorvusSKK
-
ExecutionSigned 32-bit integer overflows during size parsing
-
ImpactMalicious data written to local dictionary file
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Integer overflow checks
MITRE ATT&CK
1 technique across 1 tactic: Execution The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires CorvusSKK (any version prior to 3.3.4) to be installed on Windows 10 (build 14393 or later) or Windows 11. The critical limiting condition is active user interaction: the victim must open, import, or otherwise process an attacker-supplied tar-format dictionary file within CorvusSKK (CVSS UI:R). No elevated system privileges or special configuration are required for the overflow to trigger (CVSS PR:N), but the attack is confined to the local attack vector (AV:L) - exploitation cannot occur over the network without first delivering the malicious file to the target. There is no evidence that default-installed CorvusSKK auto-loads dictionary files from remote sources, further constraining opportunistic exploitation. |
| Impact | The CVSS 3.0 base score of 4.4 (Medium) is consistent with the constrained attack surface: AV:L requires the attack occur locally or via a file the user processes, AC:L indicates low complexity once the malicious file is in hand, PR:N signals no system privileges are needed, but UI:R is the key limiting factor - a user must actively open a malicious dictionary file. Impact is bounded to low integrity and low availability, with no confidentiality exposure. EPSS data is absent from the available intelligence, preventing quantitative exploitation probability assessment. The vulnerability is not listed in the CISA KEV catalog and no public proof-of-concept has been identified, so real-world exploitation opportunity appears low. The combination of local-only vector, mandatory user interaction, and narrow product footprint (niche Japanese IME) makes this a low operational priority for most organizations unless they specifically distribute or receive dictionary files from untrusted external sources. |
| Exploit ScenarioDerived | An attacker crafts a tar-format dictionary file with a specially engineered file size field designed to overflow a signed 32-bit integer when parsed by CorvusSKK. The attacker distributes this file through a Japanese IME community forum, dictionary sharing site, or via direct delivery to a targeted user. When the victim loads the malicious file into CorvusSKK, the integer overflow causes incorrect size calculations and malicious data is written into the local dictionary file. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Aug 26, 2026
CorvusSKK, a Windows-based SKK Japanese input method editor by Sasaki Nobuyuki, contains a signed 32-bit integer overflow (CWE-190) in its tar-format dictionary file size parsing, which can allow malicious data to be written to a dictionary file when a user opens a crafted input. All versions prior to 3.3.4 are affected; version 3.3.4 was released to address this flaw alongside a separate Lua-related vulnerability. No public exploit has been identified at time of analysis and the vulnerability is not listed in the CISA KEV catalog, indicating no confirmed active exploitation.
RemediationAI
Vendor-released patch: 3.3.4. Upgrade CorvusSKK to version 3.3.4 by downloading corvusskk-3.3.4.exe from https://github.com/nathancorvussolis/corvusskk/releases/tag/3.3.4. If immediate upgrade is not feasible, restrict dictionary file ingestion to files obtained exclusively from trusted internal sources and avoid opening dictionary files received via email, file-sharing platforms, or untrusted downloads; this directly addresses the user-interaction prerequisite of the vulnerability. The JVN advisory is available at https://jvn.jp/en/jp/JVN18496672/.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
CorvusSKK implements the SKK (Simple Kana-Kanji) input method for Windows and processes dictionary data packaged in tar-archive format. The root cause is CWE-190 (Integer Overflow or Wraparound): the application uses a signed 32-bit integer to represent tar header file sizes, which can overflow when a specially crafted size value is supplied, yielding an incorrect (smaller) computed size. This miscalculation propagates to subsequent buffer operations, potentially causing out-of-bounds or misdirected writes into the dictionary file. The affected CPE is cpe:2.3:a:sasaki_nobuyuki:corvusskk:*:*:*:*:*:*:*:*, covering all pre-3.3.4 releases. The fix described in the 3.3.4 release notes explicitly resolves 'signed 32-bit integer overflow in tar file size,' confirming the narrow technical scope of the integer type mismatch.
Know when Corvusskk gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:A/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N
Local vector requires user to open a malicious file; UI:R is mandatory; no privileges needed; impact is limited to dictionary file integrity and availability only.
Primary rating from Vendor (jpcert).
CVSS VectorVendor: jpcert
Lifecycle Timeline
2DescriptionCVE.org
CorvusSKK contains an integer overflow vulnerability, which may allow malicious data to be written to a dictionary file.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
A buffer overflow occurs when a program writes more data to a memory buffer than it was allocated to hold, causing the excess data to spill into adjacent memory regions.
Integer overflow occurs when an arithmetic operation produces a result that exceeds the maximum value a given integer type can store.
EUVD-2026-66245
GHSA-887v-ff5v-mfhj
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB