CVE-2026-111497: Native Brotli Decoder Remote Code Execution and Memory Disclosure
Bulletin ID: 2026-155-AWS
Scope: AWS
Content Type: Important (requires attention)
Publication Date: 10/28/2026 15:00 PM PDT
Last Updated Date: 11/09/2026 16:00 PM PST
Description:
AWS is aware of CVE-2026-111497, a buffer overflow in the native Brotli decompression library, first addressed in the Node.js October 2026 security releases. Decoding specially crafted Brotli-compressed input could allow a third party to run code or read process memory in an affected application. The issue affects Brotli decoding beyond Node.js, and fixes from other vendors are not yet fully available.
The information for affected AWS services is provided below. We will update this bulletin as more information becomes available.
Current Mitigation Status:
AWS Lambda
The AWS Lambda managed service is not affected. The Lambda runtimes for .NET and Node.js are affected by this issue.
Lambda runtimes for Python, Ruby, and OS-only (provided.al2023) do not include the Brotli library. If you include the Brotli library in your own function deployment in these situations, we recommend redeploying with a patched version.
- Status by runtime:
- Node.js 22, 24, 26
- Container base images: Updated. Rebuild and redeploy now.
- ZIP packages: Updated. Lambda Node.js runtimes are now using the latest versions of Node.js (22.23.4, 24.22.2, and 26.13.0).
- .NET 8, 9 (container only), 10
- Container base images: Updated.
- ZIP packages: Updated. - Note: Deprecated runtimes, including Node.js 18 and 20, do not receive security updates. We recommend that you update to a newer version.
- How to verify your function is updated: The runtime patch version is reported in the `INIT_START` line in your function logs. This line is emitted on each execution environment cold start and appears at the top of each log stream. For Node.js, look for `nodejs:22.mainline.v157` or higher (Node.js 22), `nodejs:24.mainline.v115` or higher (Node.js 24), or `nodejs:26.mainline.v73` or higher (Node.js 26). For .NET, look for `dotnet:8.mainline.v165` or higher (.NET 8) or `dotnet:10.mainline.v113` or higher (.NET 10).
If your function is on Manual or Function Update mode, we recommend that you move to Auto mode to take this update.
For more information, see Managing Lambda runtime updates.
AWS Amplify
AWS Amplify Hosting compute (Server-Side Rendering) applications running on Node.js 22 and Node.js 24 received the security update automatically. No customer action is required.
If your runtime configuration specifies a Node.js version earlier than 22, we advise migrating to a supported Node.js version (22 or 24) to receive this and future security updates.
AWS App Runner
An updated App Runner managed Node.js runtime was deployed to all AWS Regions on October 26, 2026.
- Services that have not been deployed since October 26, 2026: Redeploy your service once. The next deployment picks up the updated runtime with no configuration change.
- Services pinned to an explicit older runtime version: Update the runtime version pin first, then redeploy. A redeploy alone does not move a pinned service to the updated runtime.
Amazon CloudWatch Synthetics
- Node.js canaries: Node.js canary runtimes use the Lambda managed runtime and receive the same Lambda runtime updates described above. No action is required for canaries that receive automatic runtime updates.
- Python Selenium canaries: The Python Selenium canary runtime includes the Brotli library. We have released runtime version syn-python-selenium-14.0, which updates Brotli to version 1.2.1 to address this issue. Customers using Python Selenium canaries should update their canaries to syn-python-selenium-14.0.
AWS CodeBuild
Updated CodeBuild curated images are deployed in all Regions. The updated images include Node.js 22.23.4, 24.22.1, and 26.12.1; Ubuntu libbrotli1 1.0.9-2ubuntu0.1 / 1.1.0-2ubuntu0.1; and Amazon Linux 2023 brotli 1.1.0-1.amzn2023.0.2.
- Curated images using the latest tag with "Always use the latest image" selected, and on-demand AMI builds: No action required. Your next build uses the updated image.
- Curated images pinned to a specific version or digest: Update the reference to the updated image.
- Custom images built from a CodeBuild curated base image: Rebuild your image from the updated base image.
- Buildspecs that select Node.js 18 or 20: Updated images no longer include Node.js 18 or 20. Update your buildspec to use Node.js 22, 24, or 26.
AWS Elastic Beanstalk
Elastic Beanstalk Node.js platform version 6.11.12, which includes Node.js 24.22.1 and 22.23.4, was released on October 22, 2026.
- Environments with managed platform updates enabled: Your environment is updated to the fixed platform version during your next weekly maintenance window. To update sooner, apply the update from the Managed updates tab in the Elastic Beanstalk console.
- All other environments: Update your environment to platform version 6.11.12 or later.
- Environments on Node.js 18 or 20: Migrate to a supported Node.js platform branch.
To verify, run node --version on your environment instances.
Amazon SageMaker AI
Amazon SageMaker Autopilot: AWS has deployed a mitigation to the Autopilot data ingestion pipeline in all AWS Regions. It rejects datasets that use Brotli-compressed columns before they are decoded. Updated Autopilot and Autogluon training images that include the patched Brotli library are being deployed, and that deployment is in progress. We will update this bulletin when it is complete. These components are managed by AWS; no action is required.
Amazon SageMaker Canvas: An update to the Canvas application that includes the patched Brotli library is in progress. We will update this bulletin when it is complete. No action is required.
Amazon SageMaker Processing: A patch to the spark-processing image is in review. After the updated image is released, start new processing jobs to use the patched version. We will update this bulletin when the image is available.
Amazon SageMaker Data Wrangler: An update to the Data Wrangler container that includes the patched Brotli library is in progress. We will update this bulletin when it is complete. No action is required.
Amazon SageMaker AI built-in framework containers (XGBoost and scikit-learn): Updated images that include the patched Brotli library have been released for all supported versions: XGBoost 3.2-0 and 3.0-5, and scikit-learn 1.9-0. To pick up the update, start new training jobs or redeploy your endpoints using the latest image for your version. For XGBoost 3.0-5, the Brotli library used by pyarrow is patched; the image's Ubuntu 20.04 system libbrotli1 package has a fix available only through Ubuntu Pro, so we recommend XGBoost 3.2-0 for the latest base OS. Containers that have reached end of patch do not receive this update.
Amazon SageMaker Batch Transform: The Batch Transform service is not affected. Batch Transform does not decode Brotli-compressed data when it reads, splits, or delivers your input. Your input data, including Parquet files, is passed unchanged to the model container that you specify, which runs on instances dedicated to your job. No action is required for the Batch Transform service.
AWS Deep Learning Containers (DLC): The images below include the patched Brotli library (pyarrow 26.0.1). Pull the latest image for your framework version and restart or redeploy your workloads. To verify, run `python -c "import pyarrow; print(pyarrow.__version__)"` in the container and confirm it reports 26.0.1 or later.
If your image is still listed as in progress, you can patch it yourself before the release by building a derived image that runs `pip install --upgrade "pyarrow>=26.0.1"`, or by running that command when your container starts. Test your workload after upgrading. Alternatively, move to a version that is already updated.
- Updated (released):
- PyTorch 2.12 (EC2 and SageMaker)
- PyTorch 2.14 (SageMaker)
- Ray Serve LLM - Update in progress (we will update this bulletin when released):
- PyTorch 2.10, 2.11, and 2.13 (EC2 and SageMaker), and PyTorch 2.14 (EC2)
- TensorFlow Training 2.21 (SageMaker)
- SGLang (EC2 and SageMaker)
- Ray Serve ML and Ray Train
Containers that have reached end of patch do not receive this update.
AWS Deep Learning AMI (DLAMI): The PyTorch DLAMIs (PyTorch 2.10 through 2.14, Amazon Linux 2023 and Ubuntu, x86\_64 and arm64) include pyarrow, which bundles the affected Brotli library. Updated PyTorch DLAMIs that include the patched library (pyarrow 26.0.1) are being released, and the release is in progress. We will update this bulletin when it is complete. To patch existing instances now, run `pip install --upgrade "pyarrow>=26.0.1"` in the PyTorch environment. Base DLAMIs do not include pyarrow and are not affected.
AWS Elemental MediaLive
AWS is updating an AWS-managed MediaLive component that includes the affected library. No action is required.
Customer-managed Node.js environments
If you run and manage your own Node.js builds on AWS — for example, on Amazon EC2 instances or in your own containers on Amazon ECS or Amazon EKS — you are responsible for updating those environments. Upgrade to Node.js 22.23.4, 24.22.1, 26.12.1, or later. Because this issue extends to other languages and applications that decode Brotli, also check whether your libraries and applications include Brotli decoding as a dependency.
Mitigation using AWS WAF
If you cannot update immediately, you can use AWS WAF to deploy a custom rule that blocks inbound requests that use Brotli content encoding (the `Content-Encoding: br` header). Before you deploy, note:
- AWS WAF inspects inbound requests only. This control does not cover Brotli data from other sources, such as responses from upstream services.
- Blocking Brotli-encoded requests blocks all Brotli-encoded uploads to the application, including normal traffic.
- The rule is an example and does not match every Brotli-encoded request.
Recommended deployment steps:
- Deploy the rule with the Count action.
- Review matched requests in Amazon CloudWatch metrics and in sampled requests.
- When you confirm that the rule does not affect normal traffic, change the action to Block. To do this, replace `"Count": {}` with `"Block": {}`.
- Set the rule priority to fit your existing rule order.
Example AWS WAF rule:
|
```json { "Name": "Node2Shell_BROTLI", "Priority": 2, "Statement": { "RegexMatchStatement": { "RegexString": "^\\s*br\\s*$", "FieldToMatch": { "SingleHeader": { "Name": "content-encoding" } }, "TextTransformations": [ { "Priority": 0, "Type": "LOWERCASE" } ] } }, "Action": { "Count": {} }, "RuleLabels": [ { "Name": "Node2Shell_Brotli" } ], "VisibilityConfig": { "SampledRequestsEnabled": true, "CloudWatchMetricsEnabled": true, "MetricName": "Node2Shell_BROTLI" } } ``` |
To switch to blocking, replace `"Count": {}` with `"Block": {}`.
Updates to AWS Managed Rules are announced through the AWS WAF managed rule group SNS notifications and the AWS WAF Developer Guide.
Recommended actions
- Migrate workloads on end-of-life Node.js versions (including Node.js 18 and 20) to a supported version. For guidance, see the Node.js release schedule.
- For customer-managed environments, upgrade to a fixed Node.js release as part of your patch management process.
- Check whether your code, dependencies, or layers include their own Brotli library, and update them as fixes become available. If no patch is yet available for an affected library or application, disable Brotli decoding until one is released.
References:
Please email aws-security@amazon.com with any security questions or concerns.