Dictionary-file corruption via TAR size overflow
Published Aug 26, 2026 · Updated Aug 26, 2026
Integer overflow in CorvusSKK before 3.3.4 allows local users to write malicious data to a legitimate dictionary file via a crafted TAR archive. The TAR importer represents an archive member's file size as a signed 32-bit integer, allowing an oversized size value to overflow during extraction. A user must cause the affected IME to import the crafted archive; the reported consequence is dictionary-file modification, not code execution.
Summary
What happened
Integer overflow in CorvusSKK before 3.3.4 allows local users to write malicious data to a legitimate dictionary file via a crafted TAR archive. The TAR importer represents an archive member's file size as a signed 32-bit integer, allowing an oversized size value to overflow during extraction. A user must cause the affected IME to import the crafted archive; the reported consequence is dictionary-file modification, not code execution.
The record
- CVE
- CVE-2026-76149
- Published
- Aug 26, 2026
- Updated
- Aug 26, 2026
- Vendor
- SASAKI Nobuyuki
- Product
- CorvusSKK
- Classifications
- CWE-190, T1565.001
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 26, 2026CVE publishedPublication date reported by the CVE source.
- Aug 26, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <3.3.4
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo