Denial of service via declared-length preallocation
Published Aug 18, 2026 · Updated Aug 19, 2026
Uncontrolled memory allocation in Amazon Ion Java before 1.12.0 allows remote attackers to interrupt service via crafted binary Ion data. The binary Ion stream cursor trusts a declared-length field and preallocates heap from that untrusted size, rather than keeping internal buffer growth proportional to the input actually consumed. Any application that parses untrusted binary Ion documents with affected releases is exposed to hangs or crashes from memory exhaustion, with no stated confidentiality or integrity impact.
Summary
What happened
Uncontrolled memory allocation in Amazon Ion Java before 1.12.0 allows remote attackers to interrupt service via crafted binary Ion data. The binary Ion stream cursor trusts a declared-length field and preallocates heap from that untrusted size, rather than keeping internal buffer growth proportional to the input actually consumed. Any application that parses untrusted binary Ion documents with affected releases is exposed to hangs or crashes from memory exhaustion, with no stated confidentiality or integrity impact.
The record
- CVE
- CVE-2026-75935
- Published
- Aug 18, 2026
- Updated
- Aug 19, 2026
- Vendor
- Amazon Ion
- Product
- Ion Java
- Classifications
- CWE-789, T1499
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 18, 2026CVE publishedPublication date reported by the CVE source.
- Aug 19, 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=1.9.0 <1.12.0
What conditions does exploitation require?
What is affected?
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