Skip to content

Security Issue: Docker image v4.19.1 has 2 CRITICAL and 6 HIGH vulnerabilities #1381

Open

Description

@himadri-bhattacharjee

Trivy scan of migrate/migrate:v4.19.1 reveals 2 CRITICAL and 6 HIGH vulnerabilities. The image is built with Go 1.25.4 which has multiple known CVEs. Alpine 3.19 base image is also EOL.

Go Version

The current image is built with Go 1.25.4. 8 of the 12 vulnerabilities are in the Go stdlib and would be resolved by upgrading to Go 1.25.8+ or Go 1.26.x. This is the single most impactful fix.

Trivy Scan Results (2026-04-01)

OS: Alpine 3.19.9 (EOL) — 6 vulnerabilities (3 MEDIUM, 3 LOW)

Go Binary — 12 vulnerabilities (2 CRITICAL, 6 HIGH, 3 MEDIUM, 1 LOW)

Severity CVE Library Installed Fixed
CRITICAL CVE-2026-33186 google.golang.org/grpc v1.74.2 1.79.3
CRITICAL CVE-2025-68121 stdlib (Go 1.25.4) v1.25.4 1.25.7
HIGH CVE-2025-61726 stdlib v1.25.4 1.25.6
HIGH CVE-2025-61728 stdlib v1.25.4 1.25.6
HIGH CVE-2025-61729 stdlib v1.25.4 1.25.5
HIGH CVE-2026-25679 stdlib v1.25.4 1.25.8
HIGH CVE-2026-24051 go.opentelemetry.io/otel/sdk v1.36.0 1.40.0
HIGH CVE-2026-32286 github.com/jackc/pgproto3/v2 v2.3.3 no fix

Suggested Fix

  1. Upgrade Go to 1.25.8+ or 1.26.x — resolves 8 of 12 vulnerabilities including 1 CRITICAL
  2. Upgrade Alpine base image to 3.21+ (3.19 is EOL)
  3. Bump google.golang.org/grpc to >= 1.79.3 (CRITICAL — authz bypass)
  4. Bump go.opentelemetry.io/otel/sdk to >= 1.40.0 (HIGH — PATH hijacking)

Environment

  • Image: migrate/migrate:v4.19.1
  • Scanner: Trivy v0.69.3
  • Scan date: 2026-04-01

Activity

  1. himadri-bhattacharjee commented on Apr 1, 2026

    @himadri-bhattacharjee
    Author

    @dependabot @dhui @HaraldNordgren any plan for next release ?

  2. himadri-bhattacharjee commented on Apr 7, 2026

    @himadri-bhattacharjee
    Author

    @dhui any plan to fix the CVE?

  3. gergo-papp commented on Apr 15, 2026

    @gergo-papp

    @dhui could we create a new release to address these in the docker images that are shipped?

  4. bismayam commented on Jul 13, 2026

    @bismayam

    @dhui Is there any schedule for next release ?

  5. nshekhawat commented on Jul 13, 2026

    @nshekhawat

    @dhui @Fontinalis any plans for next release?

  6. Fontinalis commented on Jul 14, 2026

    @Fontinalis
    Member

    @bismayam @nshekhawat @gergo-papp @himadri-bhattacharjee
    Thank you for flagging - I've started working against v4.20.0, which would mostly include bug fixes and vulnerability patches - I don't have an exact date yet.

  7. nshekhawat commented on Aug 6, 2026

    @nshekhawat

    @Fontinalis Any update on above so we can understand whether this is getting released. Thanks.

  8. mschfh commented on Aug 24, 2026

    @mschfh

    @Fontinalis Any news yet? Is there any specific change or feature missing that could be contributed to?

  9. hertzcodes commented on Aug 31, 2026

    @hertzcodes

    @Fontinalis bruh please fix this

  10. hertzcodes commented on Aug 31, 2026

    @hertzcodes

    @Fontinalis security team is raping me

  11. nshekhawat commented on Aug 31, 2026

    @nshekhawat

    @Fontinalis Same here. We are waiting for this release for quite some time specially on the security fixes. We would appreciate it if you could share an update on the current status and expected release timeline. Thanks.

  12. self-assigned this
    on Sep 4, 2026
  13. added
    securityRelates to a security scans, vulnerabilities, etc
    on Sep 4, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

securityRelates to a security scans, vulnerabilities, etc

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions