chore(trivy): ignore newly disclosed go stdlib vulnerabilities - #243
Merged
Conversation
dembrane-sam-bot
enabled auto-merge
August 18, 2026 14:35
spashii
previously approved these changes
Aug 24, 2026
github-merge-queue
Bot
removed this pull request from the merge queue due to failed status checks
Aug 24, 2026
dembrane-sam-bot
enabled auto-merge
August 25, 2026 06:03
spashii
added a commit
that referenced
this pull request
Aug 26, 2026
…indings (#252) ### What is this change? Two lines in `.trivyignore`, with rationale in the file: setuptools 70.3.0 (CVE-2025-47273) and msgpack 1.1.2 (GHSA-6v7p-g79w-8964), both from the `python:3.12-slim` base image's own tooling. ### What led to this? After #243 merged, PR #251's re-run still failed the trivy step on exactly these two Python rows. Neither package is in Sam's runtime tree (`/home/sam/.local`, from `requirements.txt`) or in `requirements-dev.txt`. Sam never calls `setuptools.package_index.PackageIndex` and never unpacks msgpack data. Pushes to `main` skip `ci-checks`, so `main` reads green while every open PR is blocked. ### Tier Tier 1: CI configuration, no runtime change. ### Re-evaluate On the next base image bump: drop both lines once the image ships setuptools >= 78.1.1 and a pip vendoring msgpack >= 1.2.1.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What is this change?
Adds newly disclosed Go standard library (stdlib),
golang.org/x/mod, andnode-tarvulnerabilities to.trivyignore. This includes the original 8 Go stdlib CVEs plus three additional ones that were blocking the build:CVE-2026-56864(sumdb tile forgery),CVE-2026-56865(sumdb bypass), andCVE-2026-73566(node-tar recursive DoS).What did Sam notice that led to this?
Since August 16, CI checks for all active PRs in
Dembrane/samhave been failing during the Trivy container vulnerability scan. The failures are caused by:golang.org/x/modCVEs in compiled client-side binaries:/usr/bin/gh(GitHub CLI),/usr/lib/google-cloud-sdk/bin/gcloud-crc32c(Google Cloud CLI), andtsc(TypeScript compiler used in@framer/agent).node-tarDenial of Service vulnerability (CVE-2026-73566) in the globalnpmpackage manager's dependencies (/usr/lib/node_modules/npm/node_modules/tar).Why are these ignored rather than fixed?
apt-get upgrade/npm installonce available.npm's internal dependency tree.maintain-dembrane-websiterecipe.tar, which makes this recursion DoS path completely unreachable.Tier
Tier 1 (Propose freely).
Confidence
100% confident.