Accepted vulnerabilities
This page lists the known HIGH and CRITICAL vulnerabilities we accept for now.
They come from the scan of the gateway image and from the Dependabot alerts on the repository’s dependencies.
Image scan
Section titled “Image scan”Every gate run scans the gateway image with Trivy 0.75.0 for known HIGH and CRITICAL vulnerabilities and fails on any that is not listed here.
It scans the linux/amd64 and the linux/arm64 image, the two platforms we publish, and fails if either one has such a vulnerability.
Vulnerabilities with no fixed version yet count too, because AWS Marketplace rejects images with known high or critical vulnerabilities whether or not a fix exists.
An accepted image vulnerability needs an entry in .trivyignore with an expiry date at most 92 days away and a row below with source image, the same date and a reason.
The gate stops when the two lists disagree or an acceptance has expired, and Trivy itself stops ignoring an entry after its date.
Each gate run also writes a CycloneDX SBOM of each platform’s image, to .gate/sbom-amd64.cdx.json and .gate/sbom-arm64.cdx.json.
What the scan does not cover
Section titled “What the scan does not cover”The scan reads the image the gate builds from the branch, and the SBOMs describe that build.
Publishing builds the image again from the same Dockerfile and does not scan the image it pushes.
That build takes the newest Wolfi base image and Wolfi packages of that moment, so a package that changed between the gate run and the publish has not been scanned.
Scanning each platform of the pushed image before its tags move is not built yet.
Dependency alerts
Section titled “Dependency alerts”GitHub Dependabot alerts are on for the repository and cover the dependencies GitHub reads from uv.lock, pyproject.toml and .github/workflows/ci.yml.
Those include the development tools in the dev dependency group, which the image does not install.
We fix a HIGH or CRITICAL alert, or accept it with a row below with source dependency, an expiry date at most 92 days away and a reason.
A dependency row has no .trivyignore entry, so accepting an alert never hides that vulnerability from the image scan.
When the image scan also finds it, the row’s source is image, dependency and it needs a .trivyignore entry as well.
The gate does not read Dependabot alerts, so a new alert does not stop it.
The gate does stop when a dependency row has expired, is more than 92 days out or gives no reason.
Accepted now
Section titled “Accepted now”None.
On 2026-10-25 the scans of the gateway image built from this branch found no HIGH or CRITICAL vulnerability in its 35 Wolfi packages or its 96 Python packages, on either platform.
On 2026-10-27 the repository had no open Dependabot alert.
| ID | Source | Package | Severity | Expires | Why we accept it | What ends it |
|---|