Process crash via heap-buffer overrun
Published Aug 12, 2026 · Updated Aug 12, 2026
Out-of-bounds write in the Base64 decoder in AWS SDK for C++ before 1.11.862 allows remote authenticated users to crash an application. The core library decoder writes past the end of its heap-allocated output buffer when generated service clients pass certain crafted Base64 input. A reachable decode path and low privileges are required; impact is confined to the decoding process, where memory can be corrupted, but remote code execution has not been demonstrated.
Summary
What happened
Out-of-bounds write in the Base64 decoder in AWS SDK for C++ before 1.11.862 allows remote authenticated users to crash an application. The core library decoder writes past the end of its heap-allocated output buffer when generated service clients pass certain crafted Base64 input. A reachable decode path and low privileges are required; impact is confined to the decoding process, where memory can be corrupted, but remote code execution has not been demonstrated.
The record
- CVE
- CVE-2026-19642
- Published
- Aug 12, 2026
- Updated
- Aug 12, 2026
- Vendor
- Amazon Web Services
- Product
- AWS SDK for C++
- Classifications
- CWE-787, CAPEC-100, T1499
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 12, 2026CVE publishedPublication date reported by the CVE source.
- Aug 12, 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 <=1.11.861
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