Skip to content

fix(ci): ignore CVE-2026-34986 in transitive go-jose dep#38

Merged
aanogueira merged 1 commit into
mainfrom
andre.nogueira/fix-ci-trivy-go-jose
May 26, 2026
Merged

fix(ci): ignore CVE-2026-34986 in transitive go-jose dep#38
aanogueira merged 1 commit into
mainfrom
andre.nogueira/fix-ci-trivy-go-jose

Conversation

@aanogueira
Copy link
Copy Markdown
Contributor

Summary

Same fix as techquestsdev/hashpad#9 — Trivy started failing on a newly-published HIGH CVE in github.com/go-jose/go-jose/v3 v3.0.4, pulled transitively via caddy:alpine (the runtime image). Caddy 2.11.3 (latest) hasn't bumped it yet, so this blocks every new PR — including #36 (deploy-pages).

Caddy itself uses go-jose v4 directly; v3 comes from some sub-dependency in its module graph. The JOSE code path is not exercised by serving static files, so the risk in our deployment is nil.

Fix

Add .trivyignore with CVE-2026-34986 plus a comment explaining rationale and drop condition (Caddy ships an image with go-jose/v3 ≥ v3.0.5).

Test plan

Trivy started failing the docker-validate job on a newly-published
HIGH CVE in github.com/go-jose/go-jose/v3 v3.0.4, pulled in
transitively by the caddy:alpine runtime image.

Caddy itself uses go-jose v4 directly; v3 comes from some
sub-dependency in its module graph and hasn't been bumped upstream
yet. The affected JOSE code path is not exercised by serving static
files, so the risk in our deployment is nil.

.trivyignore is the right surgical knob here; drop the entry once
Caddy ships an image with go-jose/v3 >= v3.0.5.

Signed-off-by: Andre Nogueira <aanogueira@protonmail.com>
@github-actions
Copy link
Copy Markdown

Dependency Review

✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.

Scanned Files

None

@codecov-commenter
Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

@aanogueira aanogueira merged commit ea9bb83 into main May 26, 2026
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants