Skip to content

Bump golang.org/x/crypto to v0.56.0 for two CVEs - #239

Merged
sduchesneau merged 1 commit into
developfrom
fix/x-crypto-cve
Sep 3, 2026
Merged

Bump golang.org/x/crypto to v0.56.0 for two CVEs#239
sduchesneau merged 1 commit into
developfrom
fix/x-crypto-cve

Conversation

@sduchesneau

Copy link
Copy Markdown
Contributor

The Docker Scout step of the Build docker image workflow now fails on develop: golang.org/x/crypto v0.55.0 carries CVE-2026-78662 and CVE-2026-56855, both HIGH, both fixed in v0.56.0. The image itself builds and pushes; only the scan gate fails.

Dependabot will not open this one on its own: neither CVE is in the GitHub Advisory Database yet (Docker Scout uses its own feed), so there is no alert to raise a security update from, and x/crypto is an indirect dependency, which the weekly grouped version-update PR does not cover.

One-line bump of the indirect requirement, nothing else changes.

@dfuse-bot

dfuse-bot commented Sep 3, 2026

Copy link
Copy Markdown
Contributor

🔍 Vulnerabilities of ghcr.io/streamingfast/firehose-core:25ef074-amd64

📦 Image Reference ghcr.io/streamingfast/firehose-core:25ef074-amd64
digestsha256:6b58bd031942fd68f55916f5d3afed16f2d09a6d3b8ef9b2ea397e2af698dc11
vulnerabilitiescritical: 0 high: 0 medium: 0 low: 0
platformlinux/amd64
size173 MB
packages509
📦 Base Image ubuntu:24.04
also known as
  • c1ca75be10a22ea09ff0b7bbe8b82ee03553a4f9b795030ee2ec921e42418fc8
  • noble
  • noble-20260810
digestsha256:1e0a86e57d247923571b75e0aaf48a1449cf8c543d51fb3e07a4a7d7bfa79316
vulnerabilitiescritical: 0 high: 0 medium: 24 low: 11

@sduchesneau
sduchesneau requested review from UlysseCorbeil and removed request for billettc September 3, 2026 17:47
@sduchesneau
sduchesneau merged commit 8590e05 into develop Sep 3, 2026
8 checks passed
@sduchesneau
sduchesneau deleted the fix/x-crypto-cve branch September 3, 2026 17:51
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.

3 participants