CVE-2026-14456 (HIGH): detected in Lambda Docker Images.

## CVE Details

| **CVE ID** | **Severity** | **Affected Package** | **Installed Version** | **Fixed Version** | **Date Published** | **Date of Scan** |
|-----------------|--------------|----------------------|-----------------------|-------------------|--------------------|------------------|
| [CVE-2026-14456](https://avd.aquasec.com/nvd/cve-2026-14456) | `HIGH` | `openssl-fips-provider-latest` | `1:3.5.7-2.amzn2023.0.1` | `1:3.5.7-2.amzn2023.0.2` | `2026-08-13T15:19:31.82Z` | `2026-09-04T10:18:17.819011539Z` |

---

## Affected Docker Images

| **Image Name** | **SHA** |
|-----------------------------|---------------------------------------|
| `public.ecr.aws/lambda/provided:latest` | `public.ecr.aws/lambda/provided@sha256:6d0bcc8c0dc09c7f74497cbde777aa0dd5bb2fb8680fcb7fcc055a31962f59cd` |
| `public.ecr.aws/lambda/provided:al2023` | `public.ecr.aws/lambda/provided@sha256:6d0bcc8c0dc09c7f74497cbde777aa0dd5bb2fb8680fcb7fcc055a31962f59cd` |
| `public.ecr.aws/lambda/python:latest` | `public.ecr.aws/lambda/python@sha256:6761a5d2b8f385b29c57b9831c435fe9e978466d461cdc79f0e8c91718bccb82` |
| `public.ecr.aws/lambda/python:3.14` | `public.ecr.aws/lambda/python@sha256:6761a5d2b8f385b29c57b9831c435fe9e978466d461cdc79f0e8c91718bccb82` |
| `public.ecr.aws/lambda/python:3.13` | `public.ecr.aws/lambda/python@sha256:f1149012308003ba66bd87de66bc574750755421506db98aae45d99cb266631d` |
| `public.ecr.aws/lambda/python:3.12` | `public.ecr.aws/lambda/python@sha256:68de52ae55887341b06936cd90dc55aba9a2742bc9f68b62f9608ce7b0778736` |
| `public.ecr.aws/lambda/nodejs:latest` | `public.ecr.aws/lambda/nodejs@sha256:3a1f5e18feeac4c6ae73739b6107ad2416425f5a9ca5e90a8c230a88484cb4bf` |
| `public.ecr.aws/lambda/nodejs:24` | `public.ecr.aws/lambda/nodejs@sha256:3a1f5e18feeac4c6ae73739b6107ad2416425f5a9ca5e90a8c230a88484cb4bf` |
| `public.ecr.aws/lambda/nodejs:22` | `public.ecr.aws/lambda/nodejs@sha256:646fbee601d3ae93bb69a90912d5a8300c096e9b92864312f848460e6e9d53fe` |
| `public.ecr.aws/lambda/java:latest` | `public.ecr.aws/lambda/java@sha256:b7874e4a6e583732a140dbb1bb97f667c9f0495171b66513ebb38b854d1b527d` |
| `public.ecr.aws/lambda/java:25` | `public.ecr.aws/lambda/java@sha256:b7874e4a6e583732a140dbb1bb97f667c9f0495171b66513ebb38b854d1b527d` |
| `public.ecr.aws/lambda/java:21` | `public.ecr.aws/lambda/java@sha256:be8dbab1aed168c27e58cfc4948b4e57c4e90ce0296ca620f7205a28abc0133d` |
| `public.ecr.aws/lambda/dotnet:latest` | `public.ecr.aws/lambda/dotnet@sha256:bd7746b8d97a4332bb71d0722b751a8c524188f8b54e21e2b99bf9c06d58c4c5` |
| `public.ecr.aws/lambda/dotnet:10` | `public.ecr.aws/lambda/dotnet@sha256:bd7746b8d97a4332bb71d0722b751a8c524188f8b54e21e2b99bf9c06d58c4c5` |
| `public.ecr.aws/lambda/dotnet:9` | `public.ecr.aws/lambda/dotnet@sha256:1da5c74125c6ba060888f7bb6f04bd91da223fb97aff3d174a6c760a009f9b93` |
| `public.ecr.aws/lambda/dotnet:8` | `public.ecr.aws/lambda/dotnet@sha256:b3c22b841aec7558a1178ae6f258ae99e09f3726bbded83d771c3de7c1d13267` |
| `public.ecr.aws/lambda/ruby:latest` | `public.ecr.aws/lambda/ruby@sha256:df8b88d4179ff30b2f8603764a74fa44fc08c99722985c5da564a019e4e75a59` |
| `public.ecr.aws/lambda/ruby:4.0` | `public.ecr.aws/lambda/ruby@sha256:df8b88d4179ff30b2f8603764a74fa44fc08c99722985c5da564a019e4e75a59` |
| `public.ecr.aws/lambda/ruby:3.4` | `public.ecr.aws/lambda/ruby@sha256:9025fc0832b3dd4c5d20b7def60906cfa3453b39fd9309c4ae9897b6b8d1a750` |
| `public.ecr.aws/lambda/ruby:3.3` | `public.ecr.aws/lambda/ruby@sha256:5f6e6c25d0ff317f7fe4ddbc1954d9599dcc7f224adda9b082910c7b817b74ae` |

---

## Description

> Issue summary: When an OpenSSL QUIC server (Listener SSL object) processes
valid QUIC Initial packets for unknown destination connection IDs, it
can allocate and queue new incoming channels without enforcing any limit.

Impact summary: A remote peer that can make many Initial packets reach the
server listener faster than the application accepts connections, can cause the
memory allocated to store the per-channel state to grow without any limits,
potentially making the QUIC listener unavailable and causing Denial of Service.

CWE: CWE-770: Allocation of Resources Without Limits or Throttling

Description: The function that handles inbound QUIC packets uses
Connection-Id from the packet header to find an existing connection
(QUIC channel). If no existing connection is found and the packet
type is INITIAL, the function treats the packet as a new connection. It
allocates a new channel object and inserts it into a queue where it
waits to be accepted by the local application with SSL_accept(3ossl).
The memory occupied by these initial channel objects may grow
without bounds if the application is not able to call SSL_accept()
frequently enough to serve these inbound connection requests.

The issue is present since OpenSSL 3.5 when the QUIC server implementation
was added.

The fix introduces a limit for pending connections. The default limit is set
to 256 pending connections (waiting to be accepted by the local application).
Applications may change the default by calling SSL_set_value_uint(3ossl).

FIPS impact: no
The FIPS module is not affected as the QUIC implementation is outside of
the OpenSSL FIPS module boundary.

---

### Remediation Steps
- Update the affected package `openssl-fips-provider-latest` from version `1:3.5.7-2.amzn2023.0.1` to `1:3.5.7-2.amzn2023.0.2`.

### About this issue
- This issue may not contain all the information about the CVE nor the images it affects.
- This issue will not be updated with new information and the list of affected images may have changed since the creation of this issue.
- For more, visit [Lambda Watchdog](https://lambdawatchdog.com).
- This issue was created automatically by Lambda Watchdog.

Start by locating the build definitions for the affected Lambda Docker images and checking how the openssl-fips-provider-latest package is supplied. Update it from 1:3.5.7-2.amzn2023.0.1 to 1:3.5.7-2.amzn2023.0.2, then verify that the listed images rebuild without the reported vulnerability.

Written by the indexing model from the issue text.