Application crash via undersized ioctl argument array
Published Jun 16, 2026 · Updated Jun 16, 2026
Heap-based buffer overflow in FuseSource Jansi 2.4.3 and earlier allows local users to crash a Java application through the JNI ioctl wrapper. The native wrapper forwards an integer argument array to ioctl without verifying that its size satisfies the selected request. Reachability requires local access to an application path that invokes the wrapper and passive user interaction; the documented consequence is heap corruption and an application crash.
Summary
What happened
Heap-based buffer overflow in FuseSource Jansi 2.4.3 and earlier allows local users to crash a Java application through the JNI ioctl wrapper. The native wrapper forwards an integer argument array to ioctl without verifying that its size satisfies the selected request. Reachability requires local access to an application path that invokes the wrapper and passive user interaction; the documented consequence is heap corruption and an application crash.
The record
- CVE
- CVE-2026-8484
- Published
- Jun 16, 2026
- Updated
- Jun 16, 2026
- Vendor
- FuseSource
- Product
- Jansi
- Classifications
- CWE-1284, CWE-122, T1499.004
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 16, 2026CVE publishedPublication date reported by the CVE source.
- Jun 16, 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 <=2.4.3
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.
Weakness, pattern, technique
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