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

## CVE Details

| **CVE ID** | **Severity** | **Affected Package** | **Installed Version** | **Fixed Version** | **Date Published** | **Date of Scan** |
|-----------------|--------------|----------------------|-----------------------|-------------------|--------------------|------------------|
| [CVE-2026-48815](https://avd.aquasec.com/nvd/cve-2026-48815) | `HIGH` | `sigstore` | `3.1.0` | `4.1.1` | `2026-07-14T21:17:01.37Z` | `2026-07-15T10:18:18.360065213Z` |

---

## Affected Docker Images

| **Image Name** | **SHA** |
|-----------------------------|---------------------------------------|
| `public.ecr.aws/lambda/nodejs:22` | `public.ecr.aws/lambda/nodejs@sha256:4330d56e02e084caa74a94ed3ce6b16c5d5e00fd2bc11bbfcb8d7de8357f5471` |

---

## Description

> sigstore-js provides JavaScript libraries for interacting with Sigstore services. Prior to 4.1.1, the documented certificateOIDs option in sigstore.verify() is accepted by the public API but discarded before verification, so required certificate extension OIDs are never checked and applications relying on certificateOIDs to restrict which certificates may sign artifacts can accept unauthorized certificates. This issue is fixed in version 4.1.1.

---

### Remediation Steps
- Update the affected package `sigstore` from version `3.1.0` to `4.1.1`.

### 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 definition for the public.ecr.aws/lambda/nodejs:22 image and how it includes sigstore 3.1.0. Update the affected package to 4.1.1, rebuild and scan the image, and confirm the vulnerable version is no longer present.

Written by the indexing model from the issue text.