CVE-2026-114938 - OpenJDK Base64 Decoder Intrinsic Out-of-Bounds Write Issue
Bulletin ID: 2026-189-AWS
Scope: AWS
Content Type: Important (requires attention)
Publication Date: 11/20/2026 19:00 PM PST
Summary:
AWS is aware of CVE-2026-114938, a memory issue in the Base64 decoder intrinsic of OpenJDK 17.0.6 and later on x86-64 processors that support AVX-512 VBMI. Affected processors include Intel Ice Lake and later and AMD Zen 4 and later. Under specific conditions, a remote, unauthenticated third party can send crafted Base64 input to an application that decodes untrusted data. This results in an out-of-bounds memory write.
Java workloads running natively on AWS Graviton processors are not affected. We have no evidence that this issue has been leveraged at this time.
We will update this bulletin as more information becomes available.
Current Mitigation Status:
Amazon Corretto: Amazon Corretto versions 27.0.1.1.4, 25.0.5.1.2, 21.0.13.1.2, 17.0.21.1.2 and updated OpenJDK packages for Amazon Linux 2 and Amazon Linux 2023 are available. Customers running Java workloads on affected x86-64 instances should update to these versions. Customers who can't update right away can set the JVM option -XX:-UseBASE64Intrinsics as an interim mitigation.
Amazon Linux: Amazon Corretto packages that resolve CVE-2026-114938 are available for Amazon Linux 2, Amazon Linux 2023 and the Amazon Linux 2027 Preview. Amazon Linux rates this issue Important (CVSS v3 8.8). Customers running Amazon Corretto 17 or later on Amazon Linux should update each installed Corretto package and restart their Java applications. No reboot is needed.
- Amazon Linux 2: java-17-amazon-corretto-17.0.21.1.2-1.amzn2.1. Advisory: ALAS2-2026-4123
- Amazon Linux 2023:
- java-17-amazon-corretto-17.0.21.1.2-1.amzn2023.1. Advisory: ALAS2023-2026-3478
- java-21-amazon-corretto-21.0.13.1.2-1.amzn2023.1. Advisory: ALAS2023-2026-3479
- java-25-amazon-corretto-25.0.5.1.2-1.amzn2023.1. Advisory: ALAS2023-2026-3480
- java-27-amazon-corretto-27.0.1.1.4-1.amzn2023.1. Advisory: ALAS2023-2026-3481 - Amazon Linux 2027 Preview:
- java-17-amazon-corretto-17.0.21.1.2-1.amzn2027.1. Advisory: ALAS2027-2026-371
- java-21-amazon-corretto-21.0.13.1.2-1.amzn2027.1. Advisory: ALAS2027-2026-372
- java-25-amazon-corretto-25.0.5.1.2-1.amzn2027.1. Advisory: ALAS2027-2026-373
- java-27-amazon-corretto-27.0.1.1.4-1.amzn2027.1. Advisory: ALAS2027-2026-374
To update:
| # Amazon Linux 2 sudo yum update java-17-amazon-corretto-17.0.21.1.2-1.amzn2.1 # Amazon Linux 2023 sudo dnf update java-17-amazon-corretto-17.0.21.1.2-1.amzn2023.1 --releasever=latest sudo dnf update java-21-amazon-corretto-21.0.13.1.2-1.amzn2023.1 --releasever=latest sudo dnf update java-25-amazon-corretto-25.0.5.1.2-1.amzn2023.1 --releasever=latest sudo dnf update java-27-amazon-corretto-27.0.1.1.4-1.amzn2023.1 --releasever=latest # Amazon Linux 2027 Preview sudo dnf update java-17-amazon-corretto-17.0.21.1.2-1.amzn2027.1 --releasever=latest sudo dnf update java-21-amazon-corretto-21.0.13.1.2-1.amzn2027.1 --releasever=latest sudo dnf update java-25-amazon-corretto-25.0.5.1.2-1.amzn2027.1 --releasever=latest sudo dnf update java-27-amazon-corretto-27.0.1.1.4-1.amzn2027.1 --releasever=latest |
Amazon Linux 2023 instances that are locked to a release version must use release 2023.12.20261117 or later to receive the updated packages. Amazon Linux 2027 Preview instances that are locked to a release version must use release 2027.0.20261117 or later.
The repository update metadata does not yet list CVE-2026-114938. Customers should update now rather than wait for security scanners to report the fix.
Amazon Linux AMIs and container images do not include Amazon Corretto by default. Only instances and containers where Corretto 17 or later has been installed are affected.
Amazon EC2: Customers running self-managed Java applications on affected Amazon EC2 instance families are responsible for updating their JDK. These families include C6i, M6i, R6i, C7i, M7i, R7i, C7a, M7a, and R7a. If you use Amazon Corretto or Amazon Linux, update as described above. If you use another OpenJDK distribution, follow your JDK provider's guidance for applying the fix. Restart the Java application after updating for the fix to take effect.
AWS Lambda: Lambda Event Functions using Lambda (default) execution environments do not support the AVX-512 VBMI instructions and are not affected. Lambda Event Functions running on Lambda Managed Instances may be affected if the selected EC2 instance type supports AVX-512 VBMI instructions (see Amazon EC2 update). We have made patched images with the Amazon Corretto versions that address the issue available at Amazon ECR Public Gallery. Customers deploying functions as container images should build and redeploy their function from the latest image available. For customers deploying Lambda functions as ZIP packages, updates to managed runtimes are in progress and will rollout in two phases: phase 1 will be completed by November 20, phase 2 will be completed by November 22. Once phase 1 is complete, you can pick the patched runtime version by updating your function code or configuration. A zero-change update is not sufficient. You can also mitigate this issue by disabling use of AVX-512 VBMI instructions in Java Base64 encoding and decoding. To do this, add the -XX:-UseBASE64Intrinsics option to the JAVA_TOOL_OPTIONS environment variable in your function configuration.
Amazon ECS on EC2 & ECS on Managed Instances: Customers running Java applications on ECS on EC2 or ECS on Managed instances are responsible for updating their JDK. These families include C6i, M6i, R6i, C7i, M7i, R7i, C7a, M7a, and R7a. If you use Amazon Corretto or Amazon Linux, update as described above. If you use another OpenJDK distribution, follow your JDK provider's guidance for applying the fix. Restart your ECS task after updating your container image to take effect.
AWS Fargate: Customers running Java applications on Fargate x86_64 architecture (whether explicitly specified in the task definition or applied by default when no architecture is specified) are responsible for updating their JDK. If you use Amazon Corretto or Amazon Linux in your container, update as described above. If you use another OpenJDK distribution, follow your JDK provider's guidance for applying the fix. Fargate graviton ARM64 tasks are unaffected. Restart your Fargate task after updating your container image to take effect.
AWS Batch: Customers who run Java applications on AWS Batch are responsible for updating the JDK. To do so, follow the instructions for the compute platform their jobs run on (Amazon ECS, Amazon EKS, Amazon EC2, or AWS Fargate).
Amazon Lightsail: Customers running self-managed Java applications on affected Amazon Lightsail instance plans are responsible for updating their JDK. The affected Lightsail instance plans are 4XL-16XL general-purpose plans (general-purpose instance plans with 16 vCPUs and above). Lightsail container service customers whose container images include an affected JDK are responsible for updating it. If you use Amazon Corretto or Amazon Linux, update as described above. If you use another OpenJDK distribution, follow your JDK provider's guidance for applying the fix. Restart the Java application after updating for the fix to take effect.
Amazon OpenSearch Service: Domains running on Graviton (ARM64) instance types are not affected. Domains running OpenSearch version 2.7 or later on x86-64 instance types may be affected, because these versions use JDK 17 or JDK 21. Domains running OpenSearch versions earlier than 2.7, or Elasticsearch versions, are not affected. We are applying a mitigation to all affected domains. The update is applied through a blue/green deployment and needs no action from you. Domains with 2 or more data nodes stay available during the update. Customers can also move their domains to Graviton-based instance types to mitigate the issue or request a manual mitigation by reaching out to AWS Support.
Interim step for customers who cannot update immediately:
If you use AWS WAF, we have deployed version 1.28 of the KnownBadInputs Managed Rule Group to help protect against attempts that send malformed Base64 text. To use these protections, pin your web ACL to version 1.28 and change the action of the new Java4Shell rules from Count to Block. Before you switch to Block, we recommend leaving the rules in Count mode and reviewing how often they match your traffic (in CloudWatch metrics, sampled requests, or AWS WAF logs). This helps you confirm they won’t block expected requests. Because of the nature of the issue, these rules provide only partial coverage, and patching is the only complete fix. Customers should make upgrading their first priority. For the latest version and details on the rules added, see the AWS WAF Managed Rules changelog and subscribe to the AWS Managed Rules SNS topic.
References:
Please email aws-security@amazon.com with any s ecurity questions or concerns.